Method and system for resolving hemisphere ambiguity using a position vector

ABSTRACT

Embodiments resolve hemisphere ambiguity at a system comprising sensors. A hand-held controller of the system emits magnetic fields. Sensors positioned within a headset of the system detect the magnetic fields. A first position and orientation of the hand-held controller is determined within a first hemisphere with respect to the headset based on the magnetic fields. A second position and orientation of the hand-held controller is determined within a second hemisphere, diametrically opposite the first hemisphere, with respect to the headset based on the magnetic fields. A normal vector is determined with respect to the headset, and a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere. A dot-product of the normal vector and the position vector is calculated, and the first position and orientation of the hand-held controller is determined to be accurate when a result of the dot-product is positive.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/520,073, filed on Jul. 23, 2019, entitled “METHOD AND SYSTEM FOR RESOLVING HEMISPHERE AMBIGUITY USING A POSITION VECTOR,” which is a non-provisional of and claims the benefit of and priority to U.S. Provisional Application No. 62/702,339, filed on Jul. 23, 2018, entitled “SYSTEMS AND METHODS FOR AUGMENTED REALITY,” which are hereby incorporated by reference in their entirety for all purposes.

This application is related to U.S. patent application Ser. No 15/859,277, filed on Dec. 29, 2017, now U.S. Pat. No. 10,650,552, issued on May 12, 2020, entitled “SYSTEMS AND METHODS FOR AUGMENTED REALITY,” the entirety of which is hereby incorporated by reference.

FIELD OF THE INVENTION

The present disclosure relates to systems and methods to localize position and orientation of one or more objects in the context of augmented reality systems.

BACKGROUND OF THE INVENTION

Modern computing and display technologies have facilitated the development of systems for so called “virtual reality” or “augmented reality” experiences, wherein digitally reproduced images or portions thereof are presented to a user in a manner wherein they seem to be, or may be perceived as, real. A virtual reality, or “VR”, scenario typically involves presentation of digital or virtual image information without transparency to other actual real-world visual input; an augmented reality, or “AR”, scenario typically involves presentation of digital or virtual image information as an augmentation to visualization of the actual world around the user.

Despite the progress made in AR and VR systems, there is a need for a better localization system in the context of AR and VR devices.

SUMMARY

The present invention relates to systems and methods to optimally interpret data input from multiple sensors; in other words, embodiments described herein refine multiple inputs into a common coherent output with less computational resources than used to correct data input from a single sensor input.

In one embodiment, a computer implemented method for resolving hemisphere ambiguity at a system comprising one or more sensors includes emitting, at a hand-held controller of the system, one or more magnetic fields. The method further includes detecting, by one or more sensors positioned within a headset of the system, the one or more magnetic fields. The method also includes determining a first position and a first orientation of the hand-held controller within a first hemisphere with respect to the headset based on the one or more magnetic fields, and determining a second position and a second orientation of the hand-held controller within a second hemisphere with respect to the headset based on the one or more magnetic fields. The second hemisphere is diametrically opposite the first hemisphere with respect to the headset. The method also includes determining a normal vector with respect to the headset, and a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere. In addition, the method includes calculating a dot-product of the normal vector and the position vector, and determining that the first position and the first orientation of the hand-held controller is accurate when a result of the dot-product is positive. The method also includes determining that the second position and the second orientation of the hand-held controller is accurate when the result of the dot-product is negative.

In one or more embodiments, the position vector is defined at a coordinate frame of the headset. The normal vector originates from the headset and extends at a predetermined angle from a horizontal line from the headset. In some embodiments, the predetermined angle is 45° angle down from the horizontal line from the headset. According to some embodiments, when the result of the dot-product is positive, the first hemisphere is identified as a front hemisphere with respect to the headset and the second hemisphere is identified as a back hemisphere with respect to the headset. In some embodiments, when the result of the dot-product is positive, the first hemisphere is identified as a front hemisphere with respect to the headset and the second hemisphere is identified as a back hemisphere with respect to the headset. In one or more embodiments, the system is an optical device. According to some embodiments, the method is performed during an initialization process of the headset.

In some embodiments, the method also includes delivering virtual content to a display based on: the first position and the first orientation when the result of the dot-product is positive; or the second position and the second orientation when the result of the dot-product is negative.

In some embodiments, data input from a first sensor is updated by a correction data input point from a second sensor. As noisy data is collected, such as by a high frequency IMU, it is periodically updated or adjusted to prevent excessive error or drift from negatively affecting system performance or interpretation of that data.

In some embodiments, a first sensor's inputs are reset to originate from a corrective input point as provided by a lower frequency and more accurate second sensor, such as radar or vision system. These more accurate sensors are operated at lower frequency to preserve computing cycles otherwise necessary to operate them at full capacity, as their input need only be to periodically ground, or update and correct the noisier data the lower frequency operation does not affect system performance.

In another embodiment, a system includes a hand-held controller comprising a magnetic field transmitter configured to emit one or more magnetic fields, a headset comprising one or more magnetic field sensors configured to detect the one or more magnetic fields, and a processor coupled to the headset configured to perform operations. The operations include determining a first position and a first orientation of the hand-held controller within a first hemisphere with respect to the headset based on the one or more magnetic fields, and determining a second position and a second orientation of the hand-held controller within a second hemisphere with respect to the headset based on the one or more magnetic fields. The second hemisphere is diametrically opposite the first hemisphere with respect to the headset. The operations also include determining a normal vector with respect to the headset, and a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere. In addition, the operations include calculating a dot-product of the normal vector and the position vector, and determining that the first position and the first orientation of the hand-held controller is accurate when a result of the dot-product is positive. The operations also include determining that the second position and the second orientation of the hand-held controller is accurate when the result of the dot-product is negative.

In still another embodiment, a computer program product is embodied in a non-transitory computer readable medium, the computer readable medium having stored thereon a sequence of instructions which, when executed by a processor causes the processor to execute a method for resolving hemisphere ambiguity at a system comprising one or more sensors includes emitting, at a hand-held controller of the system, one or more magnetic fields. The method further includes detecting, by one or more sensors positioned within a headset of the system, the one or more magnetic fields. The method also includes determining a first position and a first orientation of the hand-held controller within a first hemisphere with respect to the headset based on the one or more magnetic fields, and determining a second position and a second orientation of the hand-held controller within a second hemisphere with respect to the headset based on the one or more magnetic fields. The second hemisphere is diametrically opposite the first hemisphere with respect to the headset. The method also includes determining a normal vector with respect to the headset, and a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere. In addition, the method includes calculating a dot-product of the normal vector and the position vector, and determining that the first position and the first orientation of the hand-held controller is accurate when a result of the dot-product is positive. The method also includes determining that the second position and the second orientation of the hand-held controller is accurate when the result of the dot-product is negative.

In some embodiments, a computer-implemented method includes detecting, based on data output by one or more sensors positioned within a headset of a system, one or more magnetic fields emitted by an electronic device in an environment of the system. The method also includes determining a first position and a first orientation of the electronic device within a first hemisphere with respect to the headset based on the one or more magnetic fields. The method further includes determining a normal vector with respect to the headset, and a position vector identifying a position of the electronic device with respect to the headset in the first hemisphere. The method also includes calculating a dot-product of the normal vector and the position vector, and determining whether the calculated dot-product is positive or negative in value. The method further includes delivering virtual content to a display of the headset based at least in part on determining whether the calculated dot-product is positive or negative in value.

In one or more embodiments, the electronic device comprises a hand-held controller, a wearable device, or a mobile computing device. In some embodiments, in response to determining that the calculated dot-product is positive in value, delivering virtual content to the display of the headset comprises delivering virtual content to the display of the headset based at least in part on the first position and the first orientation of the electronic device.

In some embodiments, the method includes determining a second position and a second orientation of the electronic device within a second hemisphere with respect to the headset based on the one or more magnetic fields. The second hemisphere is diametrically opposite the first hemisphere with respect to the headset. In response to determining that the calculated dot-product is negative in value, delivering virtual content to the display of the headset comprises: delivering virtual content to the display of the headset based at least in part on the second position and the second orientation of the electronic device.

In some embodiments, noisy data is adjusted by a coefficient value to pre-emptively adjust incoming data points a sensor provides. As a corrective data point is received, the system “steers” the incoming noisy data towards the corrective input point rather than completely adjusting the noisy data to the corrective input point. These embodiments are particularly beneficial when there are large changes in both sensor inputs, as a noisy data stream that steers towards a corrective input will not originate from a corrective input point in the past that is substantially different than a current measurement would indicate. In other words, the noisy data stream will not originate from an obsolete corrective input point.

In some embodiments, pose prediction is made by estimating a future position of a user and accessing features and points expected at that future position. For example, if a user is walking around a square table, features such as corners of the table or lines of objects on the table are “fetched” by the system based on where the system estimates the user will be at a future time. When the user is at that location, an image is collected and the fetched features are projected onto that image to determine a correlation and determine a specific pose. This is beneficial as it avoids feature mapping concurrent with receiving an image and reduces computational cycles by completing pre-processing of the fetched features (such as warping) prior to the image being received, so that when the image of current pose is collected the points can be more quickly applied and estimated pose is refined rather than generated, allowing virtual content to either render at that new pose more quickly or with less jitter.

Additional embodiments, advantages, and details are described in greater detail below with specific reference to the following figures as appropriate.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an augmented reality scenario with certain virtual reality object according to some embodiments.

FIGS. 2A-2D illustrates various configurations of components comprising a visual display system according to some embodiments.

FIG. 3 illustrates remote interaction with cloud computing assets according to some embodiments.

FIG. 4 illustrates an electromagnetic tracking system according to some embodiments.

FIG. 5 depicts a method of electromagnetic tracking according to some embodiments.

FIG. 6 illustrates an electromagnetic tracking system coupled to a visual display system according to some embodiments.

FIG. 7 depicts a method of determining metrics of a visual display system coupled to an electromagnetic emitter according to some embodiments.

FIG. 8 illustrates a visual display system comprising various sensing components and accessories according to some embodiments.

FIGS. 9A-9F illustrate various control modules according to various embodiments.

FIG. 10 illustrates a head mounted visual display with a minimized form factor according to some embodiments.

FIGS. 11A-11B illustrate various configurations of electromagnetic sensing modules.

FIGS. 12A-12E illustrate various configurations for electromagnetic sensor cores according to some embodiments.

FIGS. 13A-13C illustrate various time division multiplexing of electromagnetic sensing according to some embodiments.

FIGS. 14-15 depict a methods of combining various sensor data upon initiation of a visual display system according to some embodiments.

FIGS. 16A-16B illustrate a visual display system comprising various sensing and imaging components and accessories according to some embodiments.

FIGS. 17A-17G illustrate various configurations of transmission coils in electromagnetic tracking systems according to some embodiments.

FIGS. 18A-18C illustrate signal interference effects from various system inputs according to some embodiments.

FIG. 19 illustrate a calibration configuration according to some embodiments.

FIGS. 20A-20C illustrate various summing amplifier configurations as between multiple subsystems.

FIG. 21 illustrates signal overlap of multiple inputs with various signal frequencies.

FIGS. 22A-22C illustrate various arrays of electromagnetic sensing modules according to some embodiments.

FIGS. 23A-23C illustrate recalibration of sensors with a given known input according to some embodiments.

FIGS. 24A-24D illustrate determining a variable in a calibration protocol according to some embodiments.

FIGS. 25A-25E illustrate potential false readings given certain sensor inputs and applied solutions according to some embodiments.

FIG. 25F illustrates a flowchart describing determining a correct pose of a hand-held controller using a position vector for the hand-held device relative to the headset according to some embodiments.

FIG. 26 illustrates feature matching as between two images according to some embodiments.

FIGS. 27A-27B depict methods of determining pose given sensor input according to some embodiments.

FIGS. 28A-28G illustrates various sensor fusion corrections according to some embodiments.

FIG. 29 illustrates a single pathway multiple layer convolutional computing architecture according to some embodiments.

FIGS. 30A-30E illustrate various coil configurations for an electromagnetic tracking system according to some embodiments.

FIG. 31 illustrates a simplified computer system according to an embodiment described herein.

DETAILED DESCRIPTION

For example, referring to FIG. 1, an augmented reality scene (4) is depicted wherein a user of an AR technology sees a real-world park-like setting (6) featuring people, trees, buildings in the background, and a concrete platform (1120). In addition to these items, the user of the AR technology also perceives that he “sees” a robot statue (1110) standing upon the real-world platform (1120), and a cartoon-like avatar character (2) flying by which seems to be a personification of a bumble bee, even though these elements (2, 1110) do not exist in the real world. As it turns out, the human visual perception system is very complex, and producing a VR or AR technology that facilitates a comfortable, natural-feeling, rich presentation of virtual image elements amongst other virtual or real-world imagery elements is challenging.

For instance, head-worn AR displays (or helmet-mounted displays, or smart glasses) typically are at least loosely coupled to a user's head, and thus move when the user's head moves. If the user's head motions are detected by the display system, the data being displayed can be updated to take the change in head pose into account.

As an example, if a user wearing a head-worn display views a virtual representation of a three-dimensional (3D) object on the display and walks around the area where the 3D object appears, that 3D object can be re-rendered for each viewpoint, giving the user the perception that he or she is walking around an object that occupies real space. If the head-worn display is used to present multiple objects within a virtual space (for instance, a rich virtual world), measurements of head pose (i.e., the location and orientation of the user's head) can be used to re-render the scene to match the user's dynamically changing head location and orientation and provide an increased sense of immersion in the virtual space.

In AR systems, detection or calculation of head pose can facilitate the display system to render virtual objects such that they appear to occupy a space in the real world in a manner that makes sense to the user. In addition, detection of the position and/or orientation of a real object, such as handheld device (which also may be referred to as a “totem”), haptic device, or other real physical object, in relation to the user's head or AR system may also facilitate the display system in presenting display information to the user to enable the user to interact with certain aspects of the AR system efficiently. As the user's head moves around in the real world, the virtual objects may be re-rendered as a function of head pose, such that the virtual objects appear to remain stable relative to the real world. At least for AR applications, placement of virtual objects in spatial relation to physical objects (e.g., presented to appear spatially proximate a physical object in two- or three-dimensions) may be a non-trivial problem.

For example, head movement may significantly complicate placement of virtual objects in a view of an ambient environment. Such is true whether the view is captured as an image of the ambient environment and then projected or displayed to the end user, or whether the end user perceives the view of the ambient environment directly. For instance, head movement will likely cause a field of view of the end user to change, which will likely require an update to where various virtual objects are displayed in the field of the view of the end user.

Additionally, head movements may occur within a large variety of ranges and speeds. Head movement speed may vary not only between different head movements, but within or across the range of a single head movement. For instance, head movement speed may initially increase (e.g., linearly or not) from a starting point, and may decrease as an ending point is reached, obtaining a maximum speed somewhere between the starting and ending points of the head movement. Rapid head movements may even exceed the ability of the particular display or projection technology to render images that appear uniform and/or as smooth motion to the end user.

Head tracking accuracy and latency (i.e., the elapsed time between when the user moves his or her head and the time when the image gets updated and displayed to the user) have been challenges for VR and AR systems. Especially for display systems that fill a substantial portion of the user's visual field with virtual elements, it is critical that the accuracy of head-tracking is high and that the overall system latency is very low from the first detection of head motion to the updating of the light that is delivered by the display to the user's visual system. If the latency is high, the system can create a mismatch between the user's vestibular and visual sensory systems, and generate a user perception scenario that can lead to motion sickness or simulator sickness. If the system latency is high, the apparent location of virtual objects will appear unstable during rapid head motions.

In addition to head-worn display systems, other display systems can benefit from accurate and low latency head pose detection. These include head-tracked display systems in which the display is not worn on the user's body, but is, e.g., mounted on a wall or other surface. The head-tracked display acts like a window onto a scene, and as a user moves his head relative to the “window” the scene is re-rendered to match the user's changing viewpoint. Other systems include a head-worn projection system, in which a head-worn display projects light onto the real world.

Additionally, in order to provide a realistic augmented reality experience, AR systems may be designed to be interactive with the user. For example, multiple users may play a ball game with a virtual ball and/or other virtual objects. One user may “catch” the virtual ball, and throw the ball back to another user. In another embodiment, a first user may be provided with a totem (e.g., a real bat communicatively coupled to the AR system) to hit the virtual ball. In other embodiments, a virtual user interface may be presented to the AR user to allow the user to select one of many options. The user may use totems, haptic devices, wearable components, or simply touch the virtual screen to interact with the system.

Detecting head pose and orientation of the user, and detecting a physical location of real objects in space enable the AR system to display virtual content in an effective and enjoyable manner. However, although these capabilities are key to an AR system, they are difficult to achieve. In other words, the AR system must recognize a physical location of a real object (e.g., user's head, totem, haptic device, wearable component, user's hand, etc.) and correlate the physical coordinates of the real object to virtual coordinates corresponding to one or more virtual objects being displayed to the user. This requires highly accurate sensors and sensor recognition systems that track a position and orientation of one or more objects at rapid rates. Current approaches do not perform localization at satisfactory speed or precision standards.

Referring to FIGS. 2A-2D, some general componentry options are illustrated. In the portions of the detailed description which follow the discussion of FIGS. 2A-2D, various systems, subsystems, and components are presented for addressing the objectives of providing a high-quality, comfortably-perceived display system for human VR and/or AR.

As shown in FIG. 2A, an AR system user (60) is depicted wearing head mounted component (58) featuring a frame (64) structure coupled to a display system (62) positioned in front of the eyes of the user. A speaker (66) is coupled to the frame (64) in the depicted configuration and positioned adjacent the ear canal of the user (in one embodiment, another speaker, not shown, is positioned adjacent the other ear canal of the user to provide for stereo/shapeable sound control). The display (62) is operatively coupled (68), such as by a wired lead or wireless connectivity, to a local processing and data module (70) which may be mounted in a variety of configurations, such as fixedly attached to the frame (64), fixedly attached to a helmet or hat (80) as shown in the embodiment of FIG. 2B, embedded in headphones, removably attached to the torso (82) of the user (60) in a backpack-style configuration as shown in the embodiment of FIG. 2C, or removably attached to the hip (84) of the user (60) in a belt-coupling style configuration as shown in the embodiment of FIG. 2D.

The local processing and data module (70) may comprise a power-efficient processor or controller, as well as digital memory, such as flash memory, both of which may be utilized to assist in the processing, caching, and storage of data a) captured from sensors which may be operatively coupled to the frame (64), such as image capture devices (such as cameras), microphones, inertial measurement units, accelerometers, compasses, GPS units, radio devices, and/or gyros; and/or b) acquired and/or processed using the remote processing module (72) and/or remote data repository (74), possibly for passage to the display (62) after such processing or retrieval.

The local processing and data module (70) may be operatively coupled (76, 78), such as via a wired or wireless communication links, to the remote processing module (72) and remote data repository (74) such that these remote modules (72, 74) are operatively coupled to each other and available as resources to the local processing and data module (70).

In one embodiment, the remote processing module (72) may comprise one or more relatively powerful processors or controllers configured to analyze and process data and/or image information. In one embodiment, the remote data repository (74) may comprise a relatively large-scale digital data storage facility, which may be available through the internet or other networking configuration in a “cloud” resource configuration. In one embodiment, all data is stored and all computation is performed in the local processing and data module, allowing fully autonomous use from any remote modules.

Referring now to FIG. 3, a schematic illustrates coordination between the cloud computing assets (46) and local processing assets, which may, for example reside in head mounted componentry (58) coupled to the user's head (120) and a local processing and data module (70), coupled to the user's belt (308; therefore the component 70 may also be termed a “belt pack” 70), as shown in FIG. 3. In one embodiment, the cloud (46) assets, such as one or more server systems (110) are operatively coupled (115), such as via wired or wireless networking (wireless being preferred for mobility, wired being preferred for certain high-bandwidth or high-data-volume transfers that may be desired), directly to (40, 42) one or both of the local computing assets, such as processor and memory configurations, coupled to the user's head (120) and belt (308) as described above. These computing assets local to the user may be operatively coupled to each other as well, via wired and/or wireless connectivity configurations (44), such as the wired coupling (68) discussed below in reference to FIG. 8. In one embodiment, to maintain a low-inertia and small-size subsystem mounted to the user's head (120), primary transfer between the user and the cloud (46) may be via the link between the subsystem mounted at the belt (308) and the cloud, with the head mounted (120) subsystem primarily data-tethered to the belt-based (308) subsystem using wireless connectivity, such as ultra-wideband (“UWB”) connectivity, as is currently employed, for example, in personal computing peripheral connectivity applications.

With efficient local and remote processing coordination, and an appropriate display device for a user, such as the user interface or user display system (62) shown in FIG. 2A, or variations thereof, aspects of one world pertinent to a user's current actual or virtual location may be transferred or “passed” to the user and updated in an efficient fashion. In other words, a map of the world may be continually updated at a storage location which may partially reside on the user's AR system and partially reside in the cloud resources. The map (also referred to as a “passable world model”) may be a large database comprising raster imagery, 3-D and 2-D points, parametric information and other information about the real world. As more and more AR users continually capture information about their real environment (e.g., through cameras, sensors, IMUS, etc.), the map becomes more and more accurate and complete.

With a configuration as described above, wherein there is one world model that can reside on cloud computing resources and be distributed from there, such world can be “passable” to one or more users in a relatively low bandwidth form preferable to trying to pass around real-time video data or the like. The augmented experience of the person standing near the statue (i.e., as shown in FIG. 1) may be informed by the cloud-based world model, a subset of which may be passed down to them and their local display device to complete the view. A person sitting at a remote display device, which may be as simple as a personal computer sitting on a desk, can efficiently download that same section of information from the cloud and have it rendered on their display. Indeed, one person actually present in the park near the statue may take a remotely-located friend for a walk in that park, with the friend joining through virtual and augmented reality. The system will need to know where the street is, wherein the trees are, where the statue is—but with that information on the cloud, the joining friend can download from the cloud aspects of the scenario, and then start walking along as an augmented reality local relative to the person who is actually in the park.

3-D points may be captured from the environment, and the pose (i.e., vector and/or origin position information relative to the world) of the cameras that capture those images or points may be determined, so that these points or images may be “tagged”, or associated, with this pose information. Then points captured by a second camera may be utilized to determine the pose of the second camera. In other words, one can orient and/or localize a second camera based upon comparisons with tagged images from a first camera. Then this knowledge may be utilized to extract textures, make maps, and create a virtual copy of the real world (because then there are two cameras around that are registered).

So at the base level, in one embodiment a person-worn system can be utilized to capture both 3-D points and the 2-D images that produced the points, and these points and images may be sent out to a cloud storage and processing resource. They may also be cached locally with embedded pose information (i.e., cache the tagged images); so the cloud may have on the ready (i.e., in available cache) tagged 2-D images (i.e., tagged with a 3-D pose), along with 3-D points. If a user is observing something dynamic, he may also send additional information up to the cloud pertinent to the motion (for example, if looking at another person's face, the user can take a texture map of the face and push that up at an optimized frequency even though the surrounding world is otherwise basically static). More information on object recognizers and the passable world model may be found in U.S. patent application Ser. No. 14/205,126, entitled “System and method for augmented and virtual reality”, which is incorporated by reference in its entirety herein, along with the following additional disclosures, which related to augmented and virtual reality systems such as those developed by Magic Leap, Inc. of Fort Lauderdale, Fla.; U.S. patent application Ser. No. 14/641,376; U.S. patent application Ser. No. 14/555,585; U.S. patent application Ser. No. 14/212,961; U.S. patent application Ser. No. 14/690,401; U.S. patent application Ser. No. 13/663,466; patent application Ser. No. 13/684,489 and U.S. GPS and other localization information may be utilized as inputs to such processing. Highly accurate localization of the user's head, totems, hand gestures, haptic devices etc. are crucial in displaying appropriate virtual content to the user.

One approach to achieve high precision localization may involve the use of an electromagnetic field coupled with electromagnetic sensors that are strategically placed on the user's AR head set, belt pack, and/or other ancillary devices (e.g., totems, haptic devices, gaming instruments, etc.).

Electromagnetic tracking systems typically comprise at least an electromagnetic field emitter and at least one electromagnetic field sensor. The sensors may measure electromagnetic fields with a known distribution. Based on these measurements a position and orientation of a field sensor relative to the emitter is determined.

Referring now to FIG. 4, an example system diagram of an electromagnetic tracking system (e.g., such as those developed by organizations such as the Biosense® division of Johnson & Johnson Corporation, Polhemus®, Inc. of Colchester, Ver., manufactured by Sixense® Entertainment, Inc. of Los Gatos, Calif., and other tracking companies) is illustrated. In one or more embodiments, the electromagnetic tracking system comprises an electromagnetic field emitter 402 which is configured to emit a known magnetic field. As shown in FIG. 4, the electromagnetic field emitter may be coupled to a power supply (e.g., electric current, batteries, etc.) to provide power to the emitter 402.

In one or more embodiments, the electromagnetic field emitter 402 comprises several coils (e.g., at least three coils positioned perpendicular to each other to produce field in the x, y and z directions) that generate magnetic fields. This magnetic field is used to establish a coordinate space. This allows the system to map a position of the sensors in relation to the known magnetic field, and helps determine a position and/or orientation of the sensors. In one or more embodiments, the electromagnetic sensors 404 a, 404 b, etc. may be attached to one or more real objects. The electromagnetic sensors 404 may comprise smaller coils in which current may be induced through the emitted electromagnetic field.

Generally the “sensor” components (404) may comprise small coils or loops, such as a set of three differently-oriented (i.e., such as orthogonally oriented relative to each other) coils coupled together within a small structure such as a cube or other container, that are positioned/oriented to capture incoming magnetic flux from the magnetic field emitted by the emitter (402), and by comparing currents induced through these coils, and knowing the relative positioning and orientation of the coils relative to each other, relative position and orientation of a sensor relative to the emitter may be calculated.

One or more parameters pertaining to a behavior of the coils and inertial measurement unit (“IMU”) components operatively coupled to the electromagnetic tracking sensors may be measured to detect a position and/or orientation of the sensor (and the object to which it is attached to) relative to a coordinate system to which the electromagnetic field emitter is coupled. In one or more embodiments, multiple sensors may be used in relation to the electromagnetic emitter to detect a position and orientation of each of the sensors within the coordinate space. The electromagnetic tracking system may provide positions in three directions (i.e., X, Y and Z directions), and further in two or three orientation angles. In one or more embodiments, measurements of the IMU may be compared to the measurements of the coil to determine a position and orientation of the sensors. In one or more embodiments, both electromagnetic (EM) data and IMU data, along with various other sources of data, such as cameras, depth sensors, and other sensors, may be combined to determine the position and orientation. This information may be transmitted (e.g., wireless communication, Bluetooth, etc.) to the controller 406. In one or more embodiments, pose (or position and orientation) may be reported at a relatively high refresh rate in conventional systems.

Conventionally an electromagnetic emitter is coupled to a relatively stable and large object, such as a table, operating table, wall, or ceiling, and one or more sensors are coupled to smaller objects, such as medical devices, handheld gaming components, or the like.

Alternatively, as described below in reference to FIG. 6, various features of the electromagnetic tracking system may be employed to produce a configuration wherein changes or deltas in position and/or orientation between two objects that move in space relative to a more stable global coordinate system may be tracked; in other words, a configuration is shown in FIG. 6 wherein a variation of an electromagnetic tracking system may be utilized to track position and orientation delta between a head-mounted component and a hand-held component, while head pose relative to the global coordinate system (say of the room environment local to the user) is determined otherwise, such as by simultaneous localization and mapping (“SLAM”) techniques using outward- capturing cameras which may be coupled to the head mounted component of the system.

The controller 406 may control the electromagnetic field generator 402, and may also capture data from the various electromagnetic sensors 404. It should be appreciated that the various components of the system may be coupled to each other through any electro-mechanical or wireless/Bluetooth means. The controller 406 may also comprise data regarding the known magnetic field, and the coordinate space in relation to the magnetic field. This information is then used to detect the position and orientation of the sensors in relation to the coordinate space corresponding to the known electromagnetic field.

One advantage of electromagnetic tracking systems is that they produce highly accurate tracking results with minimal latency and high resolution. Additionally, the electromagnetic tracking system does not necessarily rely on optical trackers, and sensors/objects not in the user's line-of-vision may be easily tracked.

It should be appreciated that the strength of the electromagnetic field v drops as a cubic function of distance r from a coil transmitter (e.g., electromagnetic field emitter 402). Thus, an algorithm may be required based on a distance away from the electromagnetic field emitter. The controller 406 may be configured with such algorithms to determine a position and orientation of the sensor/object at varying distances away from the electromagnetic field emitter.

Given the rapid decline of the strength of the electromagnetic field as one moves farther away from the electromagnetic emitter, best results, in terms of accuracy, efficiency and low latency, may be achieved at closer distances. In typical electromagnetic tracking systems, the electromagnetic field emitter is powered by electric current (e.g., plug-in power supply) and has sensors located within 20ft radius away from the electromagnetic field emitter. A shorter radius between the sensors and field emitter may be more desirable in many applications, including AR applications.

Referring now to FIG. 5, an example flowchart describing a functioning of a typical electromagnetic tracking system is briefly described. At 502, a known electromagnetic field is emitted. In one or more embodiments, the magnetic field emitter may generate magnetic fields each coil may generate an electric field in one direction (e.g., x, y or z). The magnetic fields may be generated with an arbitrary waveform.

In one or more embodiments, each of the axes may oscillate at a slightly different frequency. At 504, a coordinate space corresponding to the electromagnetic field may be determined. For example, the control 406 of FIG. 4 may automatically determine a coordinate space around the emitter based on the electromagnetic field.

At 506, a behavior of the coils at the sensors (which may be attached to a known object) may be detected. For example, a current induced at the coils may be calculated. In other embodiments, a rotation of coils, or any other quantifiable behavior may be tracked and measured. At 508, this behavior may be used to detect a position and orientation of the sensor(s) and/or known object. For example, the controller 406 may consult a mapping table that correlates a behavior of the coils at the sensors to various positions or orientations. Based on these calculations, the position in the coordinate space along with the orientation of the sensors may be determined.

In the context of AR systems, one or more components of the electromagnetic tracking system may need to be modified to facilitate accurate tracking of mobile components. As described above, tracking the user's head pose and orientation is crucial in many AR applications. Accurate determination of the user's head pose and orientation allows the AR system to display the right virtual content to the user. For example, the virtual scene may comprise a monster hiding behind a real building. Depending on the pose and orientation of the user's head in relation to the building, the view of the virtual monster may need to be modified such that a realistic AR experience is provided. Or, a position and/or orientation of a totem, haptic device or some other means of interacting with a virtual content may be important in enabling the AR user to interact with the AR system. For example, in many gaming applications, the AR system must detect a position and orientation of a real object in relation to virtual content. Or, when displaying a virtual interface, a position of a totem, user's hand, haptic device or any other real object configured for interaction with the AR system must be known in relation to the displayed virtual interface in order for the system to understand a command, etc. Conventional localization methods including optical tracking and other methods are typically plagued with high latency and low resolution problems, which makes rendering virtual content challenging in many augmented reality applications.

In one or more embodiments, the electromagnetic tracking system, discussed in relation to FIGS. 4 and 5 may be adapted to the AR system to detect position and orientation of one or more objects in relation to an emitted electromagnetic field.

Typical electromagnetic systems tend to have a large and bulky electromagnetic emitters (e.g., 402 in FIG. 4), which is problematic for AR devices. However, smaller electromagnetic emitters (e.g., in the millimeter range) may be used to emit a known electromagnetic field in the context of the AR system.

Referring now to FIG. 6, an electromagnetic tracking system may be incorporated with an AR system as shown, with an electromagnetic field emitter 602 incorporated as part of a hand-held controller 606. In one or more embodiments, the hand-held controller may be a totem to be used in a gaming scenario. In other embodiments, the hand-held controller may be a haptic device. In yet other embodiments, the electromagnetic field emitter may simply be incorporated as part of the belt pack 70. The hand-held controller 606 may comprise a battery 610 or other power supply that powers that electromagnetic field emitter 602. It should be appreciated that the electromagnetic field emitter 602 may also comprise or be coupled to an IMU 650 component configured to assist in determining positioning and/or orientation of the electromagnetic field emitter 602 relative to other components. This may be especially important in cases where both the field emitter 602 and the sensors (604) are mobile. Placing the electromagnetic field emitter 602 in the hand-held controller rather than the belt pack, as shown in the embodiment of FIG. 6, ensures that the electromagnetic field emitter is not competing for resources at the belt pack, but rather uses its own battery source at the hand-held controller 606.

In one or more embodiments, the electromagnetic sensors 604 may be placed on one or more locations on the user's headset, along with other sensing devices such as one or more IMUs or additional magnetic flux capturing coils 608. For example, as shown in FIG. 6, sensors (604, 608) may be placed on either side of the head set (58). Since these sensors are engineered to be rather small (and hence may be less sensitive, in some cases), having multiple sensors may improve efficiency and precision.

In one or more embodiments, one or more sensors may also be placed on the belt pack 70 or any other part of the user's body. The sensors (604, 608) may communicate wirelessly or through Bluetooth to a computing apparatus that determines a pose and orientation of the sensors (and the AR headset to which it is attached). In one or more embodiments, the computing apparatus may reside at the belt pack 70. In other embodiments, the computing apparatus may reside at the headset itself, or even the hand-held controller 606. The computing apparatus may in turn comprise a mapping database (e.g., passable world model, coordinate space, etc.) to detect pose, to determine the coordinates of real objects and virtual objects, and may even connect to cloud resources and the passable world model, in one or more embodiments.

As described above, conventional electromagnetic emitters may be too bulky for AR devices. Therefore the electromagnetic field emitter may be engineered to be compact, using smaller coils compared to traditional systems. However, given that the strength of the electromagnetic field decreases as a cubic function of the distance away from the field emitter, a shorter radius between the electromagnetic sensors 604 and the electromagnetic field emitter 602 (e.g., about 3-3.5 ft) may reduce power consumption when compared to conventional systems such as the one detailed in FIG. 4.

This aspect may either be utilized to prolong the life of the battery 610 that may power the controller 606 and the electromagnetic field emitter 602, in one or more embodiments. Or, in other embodiments, this aspect may be utilized to reduce the size of the coils generating the magnetic field at the electromagnetic field emitter 602. However, in order to get the same strength of magnetic field, the power may be need to be increased. This allows for a compact electromagnetic field emitter unit 602 that may fit compactly at the hand-held controller 606.

Several other changes may be made when using the electromagnetic tracking system for AR devices. Although this pose reporting rate is rather good, AR systems may require an even more efficient pose reporting rate. To this end, IMU-based pose tracking may be used in the sensors. Crucially, the IMUs must remain as stable as possible in order to increase an efficiency of the pose detection process. The IMUs may be engineered such that they remain stable up to 50-100 milliseconds. It should be appreciated that some embodiments may utilize an outside pose estimator module (i.e., IMUs may drift over time) that may enable pose updates to be reported at a rate of 10-20 Hz. By keeping the IMUs stable at a reasonable rate, the rate of pose updates may be dramatically decreased to 10-20 Hz (as compared to higher frequencies in conventional systems).

If the electromagnetic tracking system can be run at a 10% duty cycle (e.g., only pinging for ground truth every 100 milliseconds), this would be another way to save power at the AR system. This would mean that the electromagnetic tracking system wakes up every 10 milliseconds out of every 100 milliseconds to generate a pose estimate. This directly translates to power consumption savings, which may, in turn, affect size, battery life and cost of the AR device.

In one or more embodiments, this reduction in duty cycle may be strategically utilized by providing two hand-held controllers (not shown) rather than just one. For example, the user may be playing a game that requires two totems, etc. Or, in a multi-user game, two users may have their own totems/hand-held controllers to play the game. When two controllers (e.g., symmetrical controllers for each hand) are used rather than one, the controllers may operate at offset duty cycles. The same concept may also be applied to controllers utilized by two different users playing a multi-player game, for example.

Referring now to FIG. 7, an example flow chart describing the electromagnetic tracking system in the context of AR devices is described. At 702, the hand-held controller emits a magnetic field. At 704, the electromagnetic sensors (placed on headset, belt pack, etc.) detect the magnetic field. At 706, a position and orientation of the headset/belt is determined based on a behavior of the coils/IMUs at the sensors. At 708, the pose information is conveyed to the computing apparatus (e.g., at the belt pack or headset). At 710, optionally, a mapping database (e.g., passable world model) may be consulted to correlate the real world coordinates with the virtual world coordinates. At 712, virtual content may be delivered to the user at the AR headset. It should be appreciated that the flowchart described above is for illustrative purposes only, and should not be read as limiting.

Advantageously, using an electromagnetic tracking system similar to the one outlined in FIG. 6 enables pose tracking (e.g., head position and orientation, position and orientation of totems, and other controllers). This allows the AR system to project virtual content with a higher degree of accuracy, and very low latency when compared to optical tracking techniques.

Referring to FIG. 8, a system configuration is illustrated wherein featuring many sensing components. A head mounted wearable component (58) is shown operatively coupled (68) to a local processing and data module (70), such as a belt pack, here using a physical multicore lead which also features a control and quick release module (86) as described below in reference to FIGS. 9A-9F. The local processing and data module (70) is operatively coupled (100) to a hand held component (606), here by a wireless connection such as low power Bluetooth; the hand held component (606) may also be operatively coupled (94) directly to the head mounted wearable component (58), such as by a wireless connection such as low power Bluetooth. Generally where IMU data is passed to coordinate pose detection of various components, a high- frequency connection is desirable, such as in the range of hundreds or thousands of cycles/second or higher; tens of cycles per second may be adequate for electromagnetic localization sensing, such as by the sensor (604) and transmitter (602) pairings. Also shown is a global coordinate system (10), representative of fixed objects in the real world around the user, such as a wall (8). Cloud resources (46) also may be operatively coupled (42, 40, 88, 90) to the local processing and data module (70), to the head mounted wearable component (58), to resources which may be coupled to the wall (8) or other item fixed relative to the global coordinate system (10), respectively. The resources coupled to the wall (8) or having known positions and/or orientations relative to the global coordinate system (10) may include a WiFi transceiver (114), an electromagnetic emitter (602) and/or receiver (604), a beacon or reflector (112) configured to emit or reflect a given type of radiation, such as an infrared LED beacon, a cellular network transceiver (110), a RADAR emitter or detector (108), a LIDAR emitter or detector (106), a GPS transceiver (118), a poster or marker having a known detectable pattern (122), and a camera (124). The head mounted wearable component (58) features similar components, as illustrated, in addition to lighting emitters (130) configured to assist the camera (124) detectors, such as infrared emitters (130) for an infrared camera (124); also featured on the head mounted wearable component (58) are one or more strain gauges (116), which may be fixedly coupled to the frame or mechanical platform of the head mounted wearable component (58) and configured to determine deflection of such platform in between components such as electromagnetic receiver sensors (604) or display elements (62), wherein it may be valuable to understand if bending of the platform has occurred, such as at a thinned portion of the platform, such as the portion above the nose on the eyeglasses-like platform depicted in FIG. 8. The head mounted wearable component (58) also features a processor (128) and one or more IMUs (102). Each of the components preferably are operatively coupled to the processor (128). The hand held component (606) and local processing and data module (70) are illustrated featuring similar components. As shown in FIG. 8, with so many sensing and connectivity means, such a system is likely to be heavy, power hungry, large, and relatively expensive. However, for illustrative purposes, such a system may be utilized to provide a very high level of connectivity, system component integration, and position/orientation tracking. For example, with such a configuration, the various main mobile components (58, 70, 606) may be localized in terms of position relative to the global coordinate system using WiFi, GPS, or Cellular signal triangulation; beacons, electromagnetic tracking (as described above), RADAR, and LIDAR systems may provide yet further location and/or orientation information and feedback. Markers and cameras also may be utilized to provide further information regarding relative and absolute position and orientation. For example, the various camera components (124), such as those shown coupled to the head mounted wearable component (58), may be utilized to capture data which may be utilized in simultaneous localization and mapping protocols, or “SLAM”, to determine where the component (58) is and how it is oriented relative to other components.

Referring to FIGS. 9A-9F, various aspects of the control and quick release module (86) are depicted. Referring to FIG. 9A, two outer housing components are coupled together using a magnetic coupling configuration which may be enhanced with mechanical latching. Buttons (136) for operation of the associated system may be included. FIG. 9B illustrates a partial cutaway view with the buttons (136) and underlying top printed circuit board (138) shown. Referring to FIG. 9C, with the buttons (136) and underlying top printed circuit board (138) removed, a female contact pin array (140) is visible. Referring to FIG. 9D, with an opposite portion of housing (134) removed, the lower printed circuit board (142) is visible. With the lower printed circuit board (142) removed, as shown in FIG. 9E, a male contact pin array (144) is visible. Referring to the cross-sectional view of FIG. 9F, at least one of the male pins or female pins are configured to be spring-loaded such that they may be depressed along each pin's longitudinal axis; the pins may be termed “pogo pins” and generally comprise a highly conductive material, such as copper or gold. When assembled, the illustrated configuration mates 46 male pins with female pins, and the entire assembly may be quick-release decoupled in half by manually pulling it apart and overcoming a magnetic interface (146) load which may be developed using north and south magnets oriented around the perimeters of the pin arrays (140, 144). In one embodiment, an approximate 2 kg load from compressing the 46 pogo pins is countered with a closure maintenance force of about 4 kg. The pins in the array may be separated by about 1.3 mm, and the pins may be operatively coupled to conductive lines of various types, such as twisted pairs or other combinations to support USB 3.0, HDMI 2.0, I2S signals, GPIO, and MIPI configurations, and high current analog lines and grounds configured for up to about 4 amps/5 volts in one embodiment.

Referring to FIG. 10, it is helpful to have a minimized component/feature set to be able to minimize the weight and bulk of the various components, and to arrive at a relatively slim head mounted component, for example, such as that (58) featured in FIG. 10. Thus various permutations and combinations of the various components shown in FIG. 8 may be utilized.

Referring to FIG. 11A, an electromagnetic sensing coil assembly (604, i.e., 3 individual coils coupled to a housing) is shown coupled to a head mounted component (58); such a configuration adds additional geometry to the overall assembly which may not be desirable. Referring to FIG. 11B, rather than housing the coils in a box or single housing as in the configuration of FIG. 11A, the individual coils may be integrated into the various structures of the head mounted component (58), as shown in FIG. 11B. FIGS. 12A-12E illustrate various configurations for featuring a ferrite core coupled to an electromagnetic sensor to increase field sensitivity; the embodiments of FIGS. 12B-12E are lighter in weight than the solid core configuration of FIG. 12A and may be utilized to save mass.

Referring to FIGS. 13A-13C, time division multiplexing (“TDM”) may be utilized to save mass as well. For example, referring to FIG. 13A, a conventional local data processing configuration is shown for a 3-coil electromagnetic receiver sensor, wherein analog currents come in from each of the X, Y, and Z coils, go into a pre-amplifier, go into a band pass filter, through analog-to-digital conversion, and ultimately to a digital signal processor. Referring to the transmitter configuration of FIG. 13B, and the receiver configuration of FIG. 13C, time division multiplexing may be utilized to share hardware, such that each coil sensor chain doesn't require its own amplifiers, etc. In addition to removing sensor housings, and multiplexing to save on hardware overhead, signal to noise ratios may be increased by having more than one set of electromagnetic sensors, each set being relatively small relative to a single larger coil set; also the low-side frequency limits, which generally are needed to have multiple sensing coils in close proximity, may be improved to facilitate bandwidth requirement improvements. Also, there is a tradeoff with multiplexing, in that multiplexing generally spreads out the reception of radiofrequency signals in time, which results in generally dirtier signals; thus larger coil diameter may be required for multiplexed systems. For example, where a multiplexed system may require a 9 mm-side dimension cubic coil sensor box, a non-multiplexed system may only require a 7 mm-side dimension cubic coil box for similar performance; thus there are tradeoffs in minimizing geometry and mass.

In another embodiment wherein a particular system component, such as a head mounted component (58) features two or more electromagnetic coil sensor sets, the system may be configured to selectively utilize the sensor and emitter pairing that are closest to each other to optimize the performance of the system.

Referring to FIG. 14, in one embodiment, after a user powers up his or her wearable computing system (160), a head mounted component assembly may capture a combination of IMU and camera data (the camera data being used, for example, for SLAM analysis, such as at the belt pack processor where there may be more raw processing horsepower present) to determine and update head pose (i.e., position and orientation) relative to a real world global coordinate system (162). The user may also activate a handheld component to, for example, play an augmented reality game (164), and the handheld component may comprise an electromagnetic transmitter operatively coupled to one or both of the belt pack and head mounted component (166). One or more electromagnetic field coil receiver sets (i.e., a set being 3 differently-oriented individual coils) coupled to the head mounted component to capture magnetic flux from the transmitter, which may be utilized to determine positional or orientational difference (or “delta”), between the head mounted component and handheld component (168). The combination of the head mounted component assisting in determining pose relative to the global coordinate system, and the hand held assisting in determining relative location and orientation of the handheld relative to the head mounted component, allows the system to generally determine where each component is relative to the global coordinate system, and thus the user's head pose, and handheld pose may be tracked, preferably at relatively low latency, for presentation of augmented reality image features and interaction using movements and rotations of the handheld component (170).

Referring to FIG. 15, an embodiment is illustrated that is somewhat similar to that of FIG. 14, with the exception that the system has many more sensing devices and configurations available to assist in determining pose of both the head mounted component (172) and a hand held component (176, 178), such that the user's head pose, and handheld pose may be tracked, preferably at relatively low latency, for presentation of augmented reality image features and interaction using movements and rotations of the handheld component (180).

Referring to FIGS. 16A and 16B, various aspects of a configuration similar to that of FIG. 8 are shown. The configuration of FIG. 16A differs from that of FIG. 8 in that in addition to a LIDAR (106) type of depth sensor, the configuration of FIG. 16A features a generic depth camera or depth sensor (154) for illustrative purposes, which may, for example, be either a stereo triangulation style depth sensor (such as a passive stereo depth sensor, a texture projection stereo depth sensor, or a structured light stereo depth sensor) or a time or flight style depth sensor (such as a LIDAR depth sensor or a modulated emission depth sensor); further, the configuration of FIG. 16A has an additional forward facing “world” camera (124, which may be a grayscale camera, having a sensor capable of 720p range resolution) as well as a relatively high-resolution “picture camera” (156, which may be a full color camera, having a sensor capable of 2megapixel or higher resolution, for example). FIG. 16B shows a partial orthogonal view of the configuration of FIG. 16A for illustrative purposes, as described further below in reference to FIG. 16B.

Referring back to FIG. 16A and the stereo vs time-of- flight style depth sensors mentioned above, each of these depth sensor types may be employed with a wearable computing solution as disclosed herein, although each has various advantages and disadvantages. For example, many depth sensors have challenges with black surfaces and shiny or reflective surfaces. Passive stereo depth sensing is a relatively simplistic way of getting triangulation for calculating depth with a depth camera or sensor, but it may be challenged if a wide field of view (“FOV”) is required, and may require relatively significant computing resource; further, such a sensor type may have challenges with edge detection, which may be important for the particular use case at hand. Passive stereo may have challenges with textureless walls, low light situations, and repeated patterns. Passive stereo depth sensors are available from manufacturers such as Intel® and Aquifi®. Stereo with texture projection (also known as “active stereo”) is similar to passive stereo, but a texture projector broadcasts a projection pattern onto the environment, and the more texture that is broadcasted, the more accuracy is available in triangulating for depth calculation. Active stereo may also require relatively high compute resource, present challenges when wide FOV is required, and be somewhat suboptimal in detecting edges, but it does address some of the challenges of passive stereo in that it is effective with textureless walls, is good in low light, and generally does not have problems with repeating patterns.

Active stereo depth sensors are available from manufacturers such as Intel® and Aquifi®. Stereo with structured light, such as the systems developed by Primesense, Inc.® and available under the tradename Kinect®, as well as the systems available from Mantis Vision, Inc.®, generally utilize a single camera/projector pairing, and the projector is specialized in that it is configured to broadcast a pattern of dots that is known apriori. In essence, the system knows the pattern that is broadcasted, and it knows that the variable to be determined is depth. Such configurations may be relatively efficient on compute load, and may be challenged in wide FOV requirement scenarios as well as scenarios with ambient light and patterns broadcasted from other nearby devices, but can be quite effective and efficient in many scenarios. With modulated time of flight type depth sensors, such as those available from PMD Technologies®, A.G. and SoftKinetic Inc.®, an emitter may be configured to send out a wave, such as a sine wave, of amplitude modulated light; a camera component, which may be positioned nearby or even overlapping in some configurations, receives a returning signal on each of the pixels of the camera component and depth mapping may be determined/calculated. Such configurations may be relatively compact in geometry, high in accuracy, and low in compute load, but may be challenged in terms of image resolution (such as at edges of objects), multi-path errors (such as wherein the sensor is aimed at a reflective or shiny corner and the detector ends up receiving more than one return path, such that there is some depth detection aliasing. Direct time of flight sensors, which also may be referred to as the aforementioned LIDAR, are available from suppliers such as LuminAR® and Advanced Scientific Concepts, Inc.®. With these time of flight configurations, generally a pulse of light (such as a picosecond, nanosecond, or femtosecond long pulse of light) is sent out to bathe the world oriented around it with this light ping; then each pixel on a camera sensor waits for that pulse to return, and knowing the speed of light, the distance at each pixel may be calculated. Such configurations may have many of the advantages of modulated time of flight sensor configurations (no baseline, relatively wide FOV, high accuracy, relatively low compute load, etc.) and also relatively high framerates, such as into the tens of thousands of Hertz. They may also be relatively expensive, have relatively low resolution, be sensitive to bright light, and susceptible to multi-path errors; they may also be relatively large and heavy.

Referring to FIG. 16, a partial top view is shown for illustrative purposes featuring a user's eyes (12) as well as cameras (14, such as infrared cameras) with fields of view (28, 30) and light or radiation sources (16, such as infrared) directed toward the eyes (12) to facilitate eye tracking, observation, and/or image capture. The three outward-facing world-capturing cameras (124) are shown with their FOVs (18, 20, 22), as is the depth camera (154) and its FOV (24), and the picture camera (156) and its FOV (26). The depth information garnered from the depth camera (154) may be bolstered by using the overlapping FOVs and data from the other forward-facing cameras. For example, the system may end up with something like a sub-VGA image from the depth sensor (154), a 720p image from the world cameras (124), and occasionally a 2 megapixel color image from the picture camera (156). Such a configuration has 4 cameras sharing common FOV, two of them with heterogeneous visible spectrum images, one with color, and the third one with relatively low-resolution depth. The system may be configured to do a segmentation in the grayscale and color images, fuse those two and make a relatively high-resolution image from them, get some stereo correspondences, use the depth sensor to provide hypotheses about stereo depth, and use stereo correspondences to get a more refined depth map, which may be significantly better than what was available from the depth sensor only. Such processes may be run on local mobile processing hardware, or can run using cloud computing resources, perhaps along with the data from others in the area (such as two people sitting across a table from each other nearby), and end up with quite a refined mapping.

In another embodiment, all of the above sensors may be combined into one integrated sensor to accomplish such functionality.

Referring to FIGS. 17A-17G, aspects of a dynamic transmission coil tuning configuration are shown for electromagnetic tracking, to facilitate the transmission coil to operate optimally at multiple frequencies per orthogonal axis, which allows for multiple users to operate on the same system. Typically an electromagnetic tracking transmitter will be designed to operate at fixed frequencies per orthogonal axis. With such approach, each transmission coil is tuned with a static series capacitance that creates resonance only at the frequency of operation. Such resonance allows for the maximum possible current flow through the coil which, in turn, maximizes the magnetic flux generated.

FIG. 17A illustrates a typical resonant circuit used to create resonance. Element “L1” represents a single axis transmission coil at 1 mH, and with capacitance set to 52 nF, resonance is created at 22 kHz, as shown in FIG. 17B.

FIG. 17C shows the current through the system plotted versus frequency, and it may be seen that the current is maximum at the resonant frequency. If this system is expected to operate any other frequency, the operating circuit will not be at the possible maximum. FIG. 17D illustrates an embodiment of a dynamically tunable configuration. The dynamic frequency tuning may be set to achieve resonance on the coil to get maximum current flow; an example of a tunable circuit is shown in FIG. 17E, where one capacitor (“C4”) may be tuned to produce simulated data, as shown in FIG. 17F. As shown in FIG. 17F, one of the orthogonal coils of an electromagnetic tracker is simulated as “L1” and a static capacitor (“C5”) is a fixed high voltage capacitor. This high voltage capacitor will see the higher voltages due to the resonance, and so it's package size generally will be larger. C4 will be the capacitor which is dynamically switched with different values, and can thus see a lower maximum voltage and generally be a smaller geometric package to save placement space. L3 can also be utilized to fine tune the resonant frequency. FIG. 17F illustrates the resonance achieved with the higher plots (248) versus the lower plots (250); as C4 is varied in the simulation, the resonance is changed, and it is notable that the voltage across C5 (Vmid-Vout) is higher than that across C4 (Vout). This generally will allow for a smaller package part on C4 since multiples of this generally will be needed for the system, one per frequency of operation. FIG. 17G illustrates that the maximum current achieved follows the resonance regardless of voltage across capacitors.

Referring to FIGS. 18A-18C, an electromagnetic tracking system may be bounded to work below about 30 KHz, which is slightly higher than the audible range for human hearing. Referring to FIG. 18A, there may be some audio systems which create noise in the usable frequencies for such electromagnetic tracking systems. Further, audio speakers typically have magnetic fields and one or more coils which also may interfere with electromagnetic tracking systems.

Referring to FIG. 18B, a block diagram is shown for a noise cancelling configuration for electromagnetic tracking interference. Since the unintentional interference is a known entity, this knowledge can be used to cancel the interference and improve performance. In other words, the audio generated by the system may be utilized to eliminate the effects received by the receiver coil. The noise cancelling circuit may be configured to accept the corrupted signals from the EM amplifier as well as the signal from the audio system, and the noise cancelling system will cancel out the noise received from the audio speaker. FIG. 18C illustrates a plot to show an example of the how the signal can be inverted and added to cancel the interferer. V (Vnoise), the top plot, is the noise added to the system by the audio speaker. Referring to FIG. 19, in one embodiment a known pattern (such as a circular pattern) of lights or other emitters may be utilized to assist in calibration of vision systems. For example, the circular pattern may be utilized as a fiducial; as a camera or other capture device with known orientation captures the shape of the pattern while the object coupled to the pattern is reoriented, the orientation of the object, such as a hand held totem device, may be determined; such orientation may be compared with that which comes from an associated IMU device for error determination and use in calibration.

Referring to FIGS. 20A-20C, a configuration is shown with a summing amplifier to simplify circuitry between two subsystems or components of a wearable computing configuration such as a head mounted component and belt-pack component. With a conventional configuration, each of the coils (on the left of FIG. 20A) of an electromagnetic tracking sensor is associated with an amplifier, and three distinct amplified signals would be sent through the cabling to the other component. In the illustrated embodiment, the three distinct amplified signals may be directed to a summing amplifier, which produces one amplified signal that is directed down an advantageously simplified cable, each signal at a different frequency. The summing amplifier may be configured to amplify all three signals coming in; then the receiving digital signal processor, after analog-to-digital conversion, separates the signals at the other end. FIG. 20C illustrates a filter for each frequency—so the signals may be separated back out at such stage.

Referring to FIG. 21, electromagnetic (“EM”) tracking updating is relatively “expensive” in terms of power for a portable system, and may not be capable of very high frequency updating. In a “sensor fusion” configuration, more frequently updated localization information or other dynamic inputs (measurable metrics that change over time) from another sensor such as an IMU may be combined, along with data from another sensor, such as an optical sensor (such as a camera or depth camera), which may or may not be at a relatively high frequency; the net of fusing all of these inputs places a lower demand upon the EM system and provides for quicker updating. With further regard to “dynamic inputs,” other illustrative examples include temperature fluctuations, audio volume, sizing such as dimensions of or distance to certain objects, and not merely position or orientation of a user. A set of dynamic inputs represents a collection of those inputs as a function of a given variable (such as time).

Referring back to FIG. 11B, a distributed sensor coil configuration was shown. Referring to FIG. 22A, a configuration with a single electromagnetic sensor device (604), such as a box containing three orthogonal coils, one for each direction of X, Y, Z, may be coupled to the wearable component (58) for 6 degree of freedom tracking, as described above. Also as noted above, such a device may be dis-integrated, with the three sub-portions (i.e., coils) attached at different locations of the wearable component (58), as shown in FIG. 22B. Referring to FIG. 22C, to provide further design alternatives, each individual coil may be replaced with a group of similarly oriented coils, such that the overall magnetic flux for any given orthogonal direction is captured by the group (148, 150, 152) rather than by a single coil for each orthogonal direction. In other words, rather than one coil for each orthogonal direction, a group of smaller coils may be utilized and their signals aggregated to form the signal for that orthogonal direction.

Referring to FIGS. 23A-23C, it may be useful to recalibrate a wearable computing system such as those discussed herein from time to time, and in one embodiment, ultrasonic signals at the transmitter, along with a microphone at the receiver and acoustic time of flight calculation, may be utilized to determine sound propagation delay. FIG. 23A shows that in one embodiment, 3 coils on the transmitter are energized with a burst of sinewaves, and at the same time an ultrasonic transducer may be energized with a burst of sinewave, preferably of the same frequency as one of the coils. FIG. 23B illustrates that a receiver may be configured to receive the 3 EM waves using sensor coils, and the ultrasonic wave using a microphone device. Total distance may be calculated from the amplitude of the 3 EM signals; then time of flight may be calculated by comparing the timing of the microphone response with that of the EM coils (FIG. 23C). This may be used to calculate distance and calibrate the EM correction factors.

Referring to FIG. 24A, in another embodiment, in an augmented reality system featuring a camera, the distance may be calculated by measuring the size in pixels of a known-size feature on another device such as a handheld controller.

Referring to FIG. 24B, in another embodiment, in an augmented reality system featuring a depth sensor, such as an infrared (“IR”) depth sensor, the distance may be calculated by such depth sensor and reported directly to the controller.

Referring to FIGS. 24C and 24D, once total distance is known, either the camera or the depth sensor can be used to determine position in space. The augmented reality system may be configured to project one or more virtual targets to the user.

The user may align the controller to the targets, and the system calculates position from both the EM response, and from the direction of the virtual targets plus the previously calculated distance. Roll angle calibration may be done by aligning a known feature on the controller with a virtual target projected to the user; yaw and Pitch angle may be calibrated by presenting a virtual target to the user and having the user align two features on the controller with the target (much like sighting a rifle).

Referring to FIGS. 25A and 25B, there is an inherent ambiguity associated with EM tracking systems of a 6 degree of freedom devices: a receiver would generate a similar response in two diagonally opposed locations around the transmitter. Such a challenge is particularly relevant in systems wherein both the transmitter and receiver may be mobile relative to each other.

For six degree of freedom (DOF) tracking, a totem 524, which may also be referred to as a handheld controller (e.g., TX), may generate EM signals modulated on three separate frequencies, one for each axis X, Y, and Z. A wearable 522 as illustrated in FIG. 25A, which may be implemented as an AR headset 528 as illustrated in FIG. 25B, has an EM receiving component that is configured to receive EM signals on the X, Y, and Z frequencies. The position and orientation (i.e., pose) of the totem 524 can be derived based on the characteristics of the received EM signals. However, due to the symmetric nature of the EM signals, it may not be possible to determine where the totem is located (e.g., in front of the user or behind the user as illustrated with a ghost position 526) without an additional reference frame. That is, the same EM values can be obtained at the wearable 522, 528 for two diametrically opposed totem poses: the position of totem 524 in a first (e.g., front) hemisphere 542 and ghost position 526 in a second (e.g., rear) hemisphere, with a chosen plane 540 passing through the center of a sphere dividing the two hemispheres. Accordingly, for a single snapshot of received EM signals by wearable 522, 528, either pose is valid. However, when totem 524 is moved, the tracking algorithm will typically encounter errors if the wrong hemisphere is chosen due to inconsistency in the data from the various sensors. The hemisphere ambiguity arises in part due to the fact that when a six DOF tracking session is started, the initial EM totem data does not have an unequivocal absolute position. Instead, it provides a relative distance, which can be interpreted as one of two positions in the 3D volume that is divided into two equal hemispheres with the wearable (e.g., the AR headset mounted on the head of the user) centered between the two hemispheres. Thus, embodiments of the present invention provide methods and systems that resolve hemisphere ambiguity in order to enable successful tracking of the actual position of the totem.

Such ambiguity is well documented by Kuipers, where EM signals (themselves an alternating current sine output) are described as 3×3 matrix S, as a function of the EM receiver in the EM transmitter coordinate frame:

S=f(T,r)

where T is the rotation matrix from the transmitter coordinate frame to the receiver coordinate frame, and r is the EM receiver position in the EM transmitter coordinate frame. As Kuipers solution points out, however, solving for any 6 DOF position involves squaring a sine function, where a −1 position will solve for a +1 position as well, thereby creating the hemisphere ambiguity problem.

In one embodiment, one may use an IMU sensor to see if the totem 524 (e.g., the EM transmitter) is on the plus or the negative side of the symmetry axis. In an embodiment such as those described above which feature world cameras and a depth camera, one can use that information to detect whether the totem 524 is in the positive side or negative side of the reference axis. If the totem 524 is outside of the field of view of the camera and/or depth sensor, the system may be configured to decide (or the user may decide) that the totem 524 must be in the 180° zone directly behind the user, for example.

Conventionally in the art, an EM receiver (provided in the wearable 528) is defined in the EM transmitter (provided in the totem 524) coordinate frame (as illustrated in FIG. 25C). To correct for the dual possible receiver locations (i.e., the actual receiver location 528 and the false receiver location 530, which is symmetric of the actual location of the wearable 528 with respect to the transmitter 524), a designated initialization position is established to localize the device (i.e., the wearable 528) to a specific reference position, and to dismiss the alternative solution (i.e., the false receiver location 530). Such required start position may, however, conflict with the intended or desired use.

Instead, in some embodiments, the EM transmitter (provided in the totem 524) is defined in the EM receiver (provided in the wearable 528) coordinate frame, as illustrated in FIG. 25D. For such embodiments, the Kuipers solution is modified such that the transpose of S is solved for. The consequence of this S-matrix transpose operation is equivalent to treating the EM transmitter measurement as if it were the EM receiver's, and vice versa. Notably, the same hemisphere ambiguity phenomenon still exists, but is instead represented in the EM receiver's coordinate frame. That is, the possible transmitter locations are identified as the actual location of the totem 524 and the ghost position 526 (also referred to as a false transmitter location), which is symmetric to the actual location of the totem 524 with respect to the wearable 528.

As opposed to the ambiguous hemisphere appearing both at the user's location and at a false location opposite the transmitter, the EM tracking system now has a hemisphere 542 in front of the user and a hemisphere 544 behind the user, as illustrated in FIG. 25E. By placing the hemisphere boundary (e.g., the switching plane) 540 centered at this transposed receiver location (e.g., the location of the wearable 528), a plane normal vector ns 532 comes from the origin (i.e., at the receiver placed in the wearable 528), and is directed at a predetermined angle α 534 from a straight (horizontal) line taken from the wearable 528. In some embodiments, the predetermined angle α 534 may be at 45° from the straight line taken from the wearable 528. In other embodiments, the predetermined angle α 534 may be at other angles measured with respect to a straight line taken from the wearable 528 and the use of 45° is merely exemplary. Generally, if a user is holding totem 524 at waist level, the totem will generally be in the vicinity of the plane normal vector n_(s) 532 oriented at an angle of approximately 45° from the straight line taken from the wearable 528. One of ordinary skill in the art would recognize many variations, modifications, and alternatives.

If the totem 524 is within the hemisphere in front of the user (i.e., the hemisphere 542 in FIG. 25E), then the plane normal vector ns 532 the position vector p representing a position of the totem 524 will satisfy a dot product inequality relationship of n_(s)·p>0, where p is the position point of a vector defined in the receiver coordinate frame. The vector p 536 may be a vector connecting the transmitter provided at the totem 524 to the receiver provided at the wearable 528. For example, the vector p 536 may be provided at a predetermined angle β 538 from the normal vector ns 532. When the position of the transmitter (at the totem 524) is determined in the receiver coordinate frame, two position point vectors are identified: the first (positive) position point vector p 536, and a second (negative) position point vector 546 which is symmetric to the first position point vector p 536 with respect to the receiver (at the wearable 528).

To determine which hemisphere a device (e.g., the totem 524) falls in, the two possible solutions of the S matrix are applied to the dot product, and the positive number yields the correct hemisphere location. Such determination is anecdotally true as well for the described system and use cases within, as a user is very unlikely to be holding a device at arms-length behind them.

FIG. 25F illustrates a flowchart 550 describing determining a correct pose of a hand-held controller using a position vector for the hand-held device relative to the headset according to some embodiments. According to various embodiments, the steps of the flowchart 550 may be performed during an initialization process of the headset. At step 552, the hand-held controller of an optical device system emits one or more magnetic fields. At step 554, the one or more sensors positioned within a headset (e.g., a wearable by a user) of the system detects the one or more magnetic fields emitted by the hand-held controller. At step 556, a processor coupled to the headset determines a first position and a first orientation of the hand-held controller within a first hemisphere with respect to the headset based on the one or more magnetic fields. At step 558, the processor determines a second position and a second orientation of the hand-held controller within a second hemisphere with respect to the headset based on the one or more magnetic fields. The second hemisphere is diametrically opposite the first hemisphere with respect to the headset. At step 560, the processor determines (defines) a normal vector with respect to the headset, and a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere. The position vector is defined at a coordinate frame of the headset. The normal vector originates from the headset and extends at a predetermined angle from a horizontal line from the headset. In some embodiments, the predetermined angle is 45° angle down from the horizontal line from the headset. At step 562, the processor calculates a dot-product of the normal vector and the position vector. In some examples, upon calculating the dot-product of the normal vector and the position vector, the processor may determine whether a result of the dot-product is positive or negative in value.

When a result of the dot-product is determined to be positive in value, the processor determines that the first position and the first orientation of the hand-held controller is accurate at step 564. Accordingly, when result of the dot-product is positive, the first hemisphere is identified as a front hemisphere with respect to the headset and the second hemisphere is identified as a back hemisphere with respect to the headset. The system may then deliver virtual content to a display of the system based on the first position and the first orientation when the result of the dot-product is positive.

When the result of the dot-product is determined to be negative in value, the processor determines that the second position and the second orientation of the hand-held controller is accurate at step 566. Accordingly, wherein when the result of the dot-product is negative, the second hemisphere is identified as a front hemisphere with respect to the headset and the first hemisphere is identified as a back hemisphere with respect to the headset. The system may then deliver virtual content to a display of the system based on the second position and the second orientation when the result of the dot-product is negative. In some embodiments, Step 566 is not performed if the dot-product is determined to be positive (i.e., step 566 may be an optional step). Similarly, in some embodiments, step 558 is not performed if the dot-product is determined to be positive (i.e., step 558 may be an optional step).

Referring back to the embodiments above wherein outward- oriented camera devices (124, 154, 156) are coupled to a system component such as a head mounted component (58), the position and orientation of the head coupled to such head mounted component (58) may be determined using information gathered from these camera devices, using techniques such as simultaneous localization and mapping, or “SLAM” techniques (also known as parallel tracking and mapping, or “PTAM” techniques).

Understanding the position and orientation of the head of the user, also known as the user's “head pose”, in real or near-real time (i.e., preferably with low latency of determination and updating) is valuable in determining where the user is within the actual environment around him or her, and how to place and present virtual content relative to the user and the environment pertinent to the augmented or mixed reality experience of the user. A typical SLAM or PTAM configuration involves extracting features from incoming image information and using this to triangulate 3-D mapping points, and then tracking against those 3-D mapping points. SLAM techniques have been utilized in many implementations, such as in self-driving cars, where computing, power, and sensing resources may be relatively plentiful when compared with those which might be available on board a wearable computing device, such as a head mounted component (58).

Referring to FIG. 26, in one embodiment, a wearable computing device, such as a head mounted component (58), may comprise two outward-facing cameras producing two camera images (left—204, right—206). In one embodiment a relatively lightweight, portable, and power efficient embedded processor, such as those sold by Movidius®, Intel®, Qualcomm®, or Ceva®, may comprise part of the head mounted component (58) and be operatively coupled to the camera devices. The embedded processor may be configured to first extract features (210, 212) from the camera images (204, 206). If the calibration between the two cameras is known, then the system can triangulate (214) 3-D mapping points of those features, resulting in a set of sparse 3-D map points (202). This may be stored as the “map”, and these first frames may be utilized to establish the “world” coordinate system origin (208). As subsequent image information comes into the embedded processor from the cameras, the system may be configured to project the 3-D map points into the new image information, and compare with locations of 2-D features that have been detected in the image information. Thus the system may be configured to attempt to establish a 2-D to 3-D correspondence, and using a group of such correspondences, such as about six of them, the pose of the user's head (which is, of course, coupled to the head mounted device 58) may be estimated. A greater number of correspondences, such as more than six, generally means a better job of estimating the pose. Of course this analysis relies upon having some sense of where the user's head was (i.e., in terms of position and orientation) before the current images being examined. As long as the system is able to track without too much latency, the system may use the pose estimate from the most immediately previous time to estimate where the head is for the most current data. Thus is the last frame was the origin, the system may be configured to estimate that the user's head is not far from that in terms of position and/or orientation, and may search around that to find correspondences for the current time interval. Such is a basis of one embodiment of a tracking configuration.

After moving sufficiently away from the original set of map points (202), one or both camera images (204, 206) may start to lose the map points in the newly incoming images (for example, if the user's head is rotating right in space, the original map points may start to disappear to the left and may only appear in the left image, and then not at all with more rotation). Once the user has rotated too far away from the original set of map points, the system may be configured to create new map points, such as by using a process similar to that described above (detect features, create new map points)—this is how the system may be configured to keep populating the map. In one embodiment, this process may be repeated again every 10 to 20 frames, depending upon how much the user is translating and/or rotating his head relative to his environment, and thereby translating and/or rotating the associated cameras. Frames associated with newly created mapping points may be deemed “key frames,” and the system may be configured to delay the feature detection process with key frames, or alternatively, feature detection may be conducted upon each frame to try to establish matches, and then when the system is ready to create a new key frame, the system already has that associated feature detection completed. Thus, in one embodiment, the basic paradigm is to start off creating a map, and then track, track, track until the system needs to create another map or additional portion thereof.

Referring to FIG. 27A, in one embodiment, vision based pose calculation may be split into 5 stages (pre-tracking 216, tracking 218, low-latency mapping 220, latency-tolerant mapping 222, post mapping/cleanup 224) to assist with precision and optimization for embedded processor configurations wherein computation, power, and sensing resources may be limited.

With regard to pretracking (216), the system may be configured to identify which map points project into the image before the image information arrives. In other words, the system may be configured to identify which map points would project into the image given that the system knows where the user was before, and has a sense or where the user is going.

The notion of “sensor fusion” is discussed further below, but it is worth noting here that one of the inputs that the system may get from a sensor fusion module or functionality may be “post estimation” information, at a relatively fast rate, such as at 250 Hz from an inertial measurement unit (“IMU”) or other sensor or device (this is a high rate relative to, say, 30 Hz, at which the vision based pose calculation operation may be providing updates). Thus there may be a much finer temporal resolution of pose information being derived from IMU or other device relative to vision based pose calculation; but it is also noteworthy that the data from devices such as IMUS tends to be somewhat noisy and susceptible to pose estimation drift, as discussed below. For relatively short time windows, such as 10-15 milliseconds, the IMU data may be quite useful in predicting pose, and, again, when combined with other data in a sensor fusion configuration, an optimized overall result may be determined. For example, and as explained in greater detail below with reference to FIG. 28B-28G, a propagation path of collected points may be adjusted, and from that adjustment a pose at a later time may be estimated/informed by where sensor fusion determines a future point may be based on the adjusted propagation path.

Pose information coming from a sensor fusion module or functionality may be termed “pose prior”, and this pose prior may be utilized by the system to estimate which sets of points are going to project into the current image. Thus in one embodiment, the system is configured in a “pre tracking” step (216) to pre-fetch those map points and conduct some pre-processing that helps to reduce latency of overall processing. Each of the 3-D map points may be associated with a descriptor, so that the system may identify them uniquely and match them to regions in the image. For example, if a given map point was created by using a feature that has a patch around it, the system may be configured to maintain some semblance of that patch along with the map point, so that when the map point is seen projected onto other images, the system can look back at the original image used to create the map, examine the patch correlation, and determine if they are the same point. Thus in pre-processing, the system may be configured to do some amount of fetching of map points, and some amount of pre-processing associated with the patches associated with those map points. Thus in pre-tracking (216), the system may be configured to pre-fetch map points, and pre-warp image patches (a “warp” of an image may be done to ensure that the system can match the patch associated with the map point with the current image; it's a way to make sure that the data being compared is compatible).

Referring back to FIG. 27, a tracking stage may comprise several components, such as feature detection, optical flow analysis, feature matching, and pose estimation. While detecting features in the incoming image data, the system may be configured to utilize optical flow analysis to save computational time in feature detection by trying to follow features from one or more previous images. Once features have been identified in the current image, the system may be configured to try to match the features with projected map points—this may be deemed the “feature matching” portion of the configuration. In the pre-tracking stage (216), the system preferably has already identified which map points are of interest, and fetched them; in feature mapping, they are projected into the current image and the system tries to match them with the features. The output of feature mapping is the set of 2-D to 3-D correspondences, and with that in hand, the system is configured to estimate the pose.

As the user is tracking his head around, coupled to the head mounted component (58), the system preferably is configured to identify if the user is looking at a new region of the environment or not, to determine whether a new key frame is needed. In one embodiment, such analysis of whether a new key frame is needed may be almost purely based upon geometry; for example, the system may be configured to look at the distance (translational distance; also field-of-view capture reorientation—the user's head may be close translationally but re-oriented such that completely new map points are required, for example) from the current frame to the remaining key frames. Once the system has determined that a new key frame should be inserted, the mapping stage may be started. As noted above, the system may be configured to operate mapping as three different operations (low-latency mapping, latency-tolerant mapping, post/mapping or cleanup), as opposed to a single mapping operation more likely seen in a conventional SLAM or PTAM operation.

Low-latency mapping (220), which may be thought of in a simplistic form as triangulation and creation of new map points, is a critical stage, with the system preferably configured to conduct such stage immediately, because the paradigm of tracking discussed herein relies upon map points, with the system only finding a position if there are map points available to track against. The “low-latency” denomination refers to the notion that there is no tolerance for unexcused latency (in other words, this part of the mapping needs to be conducted as quickly as possible or the system has a tracking problem).

Latency-tolerant mapping (222) may be thought of in a simplistic form as an optimization stage. The overall process does not absolutely require low latency to conduct this operation known as “bundle adjustment”, which provides a global optimization in the result. The system may be configured to examine the positions of 3-D points, as well as where they were observed from. There are many errors that can chain together in the process of creating map points. The bundle adjustment process may take, for example, particular points that were observed from two different view locations and use all of this information to gain a better sense of the actual 3-D geometry.

The result may be that the 3-D points and also the calculated trajectory (i.e., location, path of the capturing cameras) may be adjusted by a small amount. It is desirable to conduct these kinds of processes to not accumulate errors through the mapping/tracking process.

The post mapping/cleanup (224) stage is one in which the system may be configured to remove points on the map that do not provide valuable information in the mapping and tracking analysis. In this stage, these points that do not provide useful information about the scene are removed, and such analysis is helpful in keeping the entire mapping and tracking process scaleable.

During the vision pose calculation process, there is an assumption that features being viewed by the outward-facing cameras are static features (i.e., not moving from frame to frame relative to the global coordinate system). In various embodiments, semantic segmentation and/or object detection techniques may be utilized to remove moving objects from the pertinent field, such as humans, moving vehicles, and the like, so that features for mapping and tracking are not extracted from these regions of the various images. In one embodiment, deep learning techniques, such as those described below, may be utilized for segmenting out these non-static objects.

In some embodiments, a pre-fetching protocol lead to pose estimation according to method (2710) as depicted in FIG. 27B. From 2710 to 2720 pose data is received over time, such that an estimated pose at a future time may be extrapolated at 2730. Extrapolation may be simple constant value extrapolation from given inputs, or corrected extrapolation based on correction input points as described below with reference to sensor fusion.

Upon determining an estimated future pose, in some embodiments the system accesses a feature map for that position. For example, if a user is walking while wearing a head mounted component, the system may extrapolate a future position based on the pace of the user and access a feature map for that extrapolated/estimated position. In some embodiments, this step is pre-fetching as described above with reference to step (216) of FIG. 27A. At (2740) specific points of the feature map are extracted, and in some embodiments, patches surrounding the points are extracted as well. At (2750) the extracted points are processed. In some embodiments, processing comprises warping the points to match an estimated orientation or find a homography of the extracted points or patches.

At (2760) a real time image (or the current view at the estimated time) is received by the system. The processed points are projected onto the received image at (2770). At 2780 the system establishes correspondences between the received image and the processed points. In some cases, the system has made a perfect estimation and the received image and processed points align perfectly, confirming the estimated pose of (2730). In other cases, the processed points do not perfectly align with features of the received images and the system performs additional warping or adjustments to determine the correct pose based on a degree of correspondence at (2790). Of course, it is possible that none of the processed points align with features in the received image, and the system would have to revert to new tracking and feature mapping as described above with reference to FIG. 27A and steps (218)-(224).

Referring to FIGS. 28A-28F, a sensor fusion configuration may be utilized to benefit from one source of information coming from a sensor with relatively high update frequency (such as an IMU updating gyro, accelerometer, and/or magnetometer data pertinent to head pose at a frequency such as 250 Hz) and another information source updating at a lower frequency (such as a vision based head pose measurement process updating at a frequency such as 30 Hz).

Referring to FIG. 28A, in one embodiment the system may be configured to use an extended Kalman filter (“EKF”, 232) and to track a significant amount of information regarding the device. For example, in one embodiment, it may account for 32 states, such as angular velocity (i.e., from the IMU gyroscope), translational acceleration (i.e., from the IMU accelerometers), calibration information for the IMU itself (i.e., coordinate systems and calibration factors for the gyros and accelerometers; the IMU may also comprise one or more magnetometers). Thus the system may be configured to take in IMU measurements at a relatively high update frequency (226), such as 250 Hz, as well as data from some other source at a lower update frequency (i.e., calculated vision pose measurement, odometry data, etc.), here vision pose measurement (228) at an update frequency such as 30 Hz.

Each time the EKF gets a round of IMU measurements, the system may be configured to integrate the angular velocity information to get rotational information (i.e., the integral of angular velocity (change in rotational position over change in time) is angular position (change in angular position)); likewise for translational information (in other words, by doing a double integral of the translational acceleration, the system will get position data). With such calculation the system is configured to get six degree-of-freedom (“DOF”) pose information from the head (translation in X, Y, Z; orientation for the three rotational axes)—at the high frequency from the IMU (i.e., 250 Hz in one embodiment). Each time an integration is done, noise is accumulated in the data; doing a double integration on the translational or rotational acceleration can propagate noise.

Generally the system is configured to not rely on such data which is susceptible to “drift” due to noise for too long a time window, such as any longer than about 100 milliseconds in one embodiment. The incoming lower frequency (i.e., updated at about 30 Hz in one embodiment) data from the vision pose measurement (228) may be utilized to operate as a correction factor with the EKF (232), producing a corrected output (230).

FIGS. 28B-28F illustrate how the data from one source at a higher update frequency may be combined with the data from another source at a lower update frequency. As depicted in FIG. 28B, a first group of dynamic input points (234), for example from a from an IMU at a higher frequency, such as 250 Hz, is shown, with a correction input point (238) coming in at a lower frequency, such as 30 Hz, such as from a vision pose calculation process. The system may be configured to correct (242) to the vision pose calculation point when such information is available, and then continue forward with a second set of dynamic input points (236) such as points from the IMU data and another correction (244) from another correction input point (240) available from the vision pose calculation process. Stated differently, the high frequency dynamic inputs collected from a first sensor may be periodically adjusted by a low frequency corrective input collected from a second sensor.

In this way, embodiments of the present invention applying corrective “updates” with the vision pose data to the “propagation path” of data coming from the IMU, using an EKF. Such update, as depicted in FIG. 28B, adjusts the propagation path of dynamic inputs (234) to a new origin at the correction input point (238), again at (240), and so on for future collection of points. In some embodiments, rather than adjust a propagation path to originate from a correction input point, a propagation path may adjusted by changing a rate of change (i.e., slope of points (236) in FIG. 28B) for the second set of dynamic inputs by a calculated coefficient. These adjustments may reduce jitter in the system by interpreting new data collection as less severe differences from a corrective input.

For example, as depicted in FIG. 28B-2, a coefficient is applied to second set of dynamic input points (236) such that the origin of the propagation path is the same as the last point of the propagation path of the first set of dynamic input points (234), but sloped less severe as compared to the rate of change of first set of dynamic input points (234). As depicted in FIG. 28B-2, the size of corrections (242) and (242) changes, but not as severe as if there had been no correction input at time T_(N), and depending on the computing resource and sensor, making two full corrections at T_(N) and T_(N+M) as shown in FIG. 28B-1 may be more computationally expensive and prone to introduce jitter between the sensors than the more subtle adjustment of FIG. 28B-2. Further, as depicted in FIG. 28B, correction input points (238) and (240) are in the same location; if those points were also moving, a user may benefit from having a slope adjustment of dynamic input points that places the last point of propagation path (236) closer to correction input point (240), as compared to an origination adjustment.

FIG. 28G depicts method 2800 of collecting a first set of dynamic points at (2810), and then collecting a correction input point at (2820). In some embodiments, method 2800 proceeds to step (2830 a) where a second set of dynamic points is collected, and the resulting propagation path of those collected points are adjusted at (2830 b) based on the correction input (such as by adjusting a recorded rate of change, or adjusting an origin of that propagation path). In some embodiments, after the correction input point is collected at (2820) an adjustment is determined at (2830 b) to be applied to dynamic points collected thereafter and at (2830 a), as second set of dynamic input points are collected the propagation path is adjusted in real time.

For systems employing sensors known to produce compounding error/noise over time and other sensors that produce low error/noise, such sensor fusion provides more economical computing resource management.

In is notable that in some embodiments, the data from the second source (i.e., such as the vision pose data) may come in not only at a lower update frequency, but also with some latency—meaning that the system preferably is configured to navigate a time domain adjustment as the information from IMU and vision pose calculation are integrated. In one embodiment, to ensure that the system is fusing in the vision pose calculation input at the correct time domain position in the IMU data, a buffer of IMU data may be maintained, to go back, to a time (say “Tx”) in the IMU data to do the fusion and calculate the “update” or adjustment at the time pertinent to the input from the vision pose calculation, and then account for that in forward propagation to the current time (say “Tcurrent”), which leaves a gap between the adjusted position and/or orientation data and the most current data coming from the IMU. To ensure that there is not too much of a “jump” or “jitter” in the presentation to the user, the system may be configured to use smoothing techniques. One way to address this issue is to use weighted averaging techniques, which may be linear, nonlinear, exponential, etc., to eventually drive the fused data stream down to the adjusted path. Referring to FIG. 28C, for example, weighted averaging techniques may be utilized over the time domain between T0 and T1 to drive the signal from the unadjusted path (252; i.e., coming straight from the IMU) to the adjusted path (254; i.e., based upon data coming from the visual pose calculation process); one example is shown in FIG. 28D, wherein a fused result (260) is shown starting at the unadjusted path (252) and time TO and moving exponentially to the adjusted path (254) by T1. Referring to FIG. 28E, a series of correction opportunities is shown with an exponential time domain correction of the fused result (260) toward the lower path from the upper path in each sequence (first correction is from the first path 252, say from the IMU, to the second path 254, say from vision based pose calculation; then continuing with the similar pattern forward, using the continued IMU data while correcting, down in this example toward successive corrected lower paths 256, 258 based upon successive points from vision pose, using each incoming vision based pose calculation point). Referring to FIG. 28F, with short enough time windows between the “updates” or corrections, the overall fused result (260) functionally may be perceived as a relatively smooth patterned result (262).

In other embodiment, rather than rely directly upon the vision pose measurement, the system may be configured to examine the derivative EKF; in other words, rather than using vision pose calculation result directly, the system uses the change in vision pose from the current time to the previous time. Such a configuration may be pursued, for example, if the amount of noise in the vision pose difference is a lot less than the amount of noise in the absolute vision pose measurement. It is preferable to not have instantaneous errors throwing off the fused result, because the output of all of this is pose, which gets sent back as the “pose prior” values to the vision system.

The external system-based “consumer” of the pose result may be termed the “Pose Service”, and the system may be configured such that all other system components tap into the Pose Service when requesting a pose at any given time. The Pose Service may be configured to be a queue or stack (i.e., a buffer), with data for a sequences of time slices, one end having the most recent data. If a request of the Pose Service is the current pose, or some other pose that is in the buffer, then it may be outputted immediately; in certain configurations, the Pose Service will receive a request for: what is the pose going to be 20 milliseconds forward in time from now (for example, in a video game content rendering scenario—it may be desirable for a related service to know that it needs to be rendering something in a given position and/or orientation slightly in the future from now). In one model for producing a future pose value, the system may be configured to use a constant velocity prediction model (i.e., assume that the user's head is moving with a constant velocity and/or angular velocity); in another model for producing a future pose value, the system may be configured to use a constant acceleration prediction model (i.e., assume that the user's head is translating and/or rotating with constant acceleration).

The data in the data buffer may be utilized to extrapolate where the pose will be using such models. A constant acceleration model uses a bit longer tail into the data of the buffer for prediction than does a constant velocity model, and we have found that the subject systems can predict into the range of 20 milliseconds in the future without substantial degradation. Thus the Pose Service may be configured to have a data buffer going back in time, as well as about 20 milliseconds or more going forward, in terms of data that may be utilized to output pose.

Operationally, content operations generally will be configured to identify when the next frame draw is going to be coming in time (for example, it will either try to draw at a time T, or at a time T+N, the N being the next interval of updated data available from the Pose Service).

The use of user-facing (i.e., inward-facing, such as toward the user's eyes) cameras, such as those depicted in FIG. 16B (14) may be utilized to conduct eye tracking, as described, for example, in U.S. patent application Ser. No. 14/707,000 and Ser. No. 15/238,516, which are incorporated by reference herein in their entirety. The system may be configured to conduct several steps in eye tracking, such as first taking an image of the eye of the user; then using segmenting analysis to segment anatomy of the eye (for example, to segment the pupil, from the iris, from the sclera, from the surrounding skin); then the system may be configured to estimate the pupil center using glint locations identified in the images of the eye, the glints resulting from small illumination sources (16), such as LEDs, which may be placed around the inward-facing side of the head mounted component (58); from these steps, the system may be configured to use geometric relationships to determine an accurate estimate regarding where in space the particular eye is gazing. Such processes are fairly computationally intensive for two eyes, particularly in view of the resources available on a portable system, such as a head mounted component (58) featuring on on-board embedded processor and limited power. Deep learning techniques may be trained and utilized to address these and other computational challenges.

For example, in one embodiment, a deep learning network may be utilized to conduct the segmentation portion of the aforementioned eye tracking paradigm (i.e., a deep convolutional network may be utilized for robust pixel-wise segmentation of the left and right eye images into iris, pupil, sclera, and rest classes), with everything else remaining the same; such a configuration takes one of the large computationally intensive portions of the process and makes it significantly more efficient. In another embodiment, one joint deep learning model may be trained and utilized to conduct segmentation, pupil detection, and glint detection (i.e., a deep convolutional network may be utilized for robust pixel-wise segmentation of the left and right eye images into iris, pupil, sclera, and rest classes; eye segmentation may then be utilized to narrow down the 2-D glint locations of active inward-facing LED illumination sources); then the geometry calculations to determine gaze may be conducted. Such a paradigm also streamlines computation. In a third embodiment, a deep learning model may be trained and utilized to directly estimate gaze based upon the two images of the eyes coming from the inward-facing cameras (i.e., in such an embodiment, a deep learning model solely using the pictures of the user's eyes may be configured to tell the system where the user is gazing in three dimensional space; a deep convolutional network may be utilized for robust pixel-wise segmentation of the left and right eye images into iris, pupil, sclera, and rest classes; eye segmentation may then be utilized to narrow down the 2-D glint locations of active inward-facing LED illumination sources; the 2-D glint locations along with 3-D LED locations may be utilized to detect the cornea center in 3-D; note that all 3-D locations may be in the respective camera coordinate system; then eye segmentation may also be utilized to detect the pupil center in the 2-D image using ellipse fitting; using offline calibration information, the 2-D pupil center may be mapped to a 3-D gaze point, with depth being determined during calibration; the line connecting the cornea 3-D location and the 3-D gaze point location is the gaze vector for that eye); such a paradigm also streamlines computation, and the pertinent deep network may be trained to directly predict the 3-D gaze point given the left and right images. The loss function for such deep network to perform such a training may be a simple Euclidean loss, or also include the well-known geometric constraints of the eye model.

Further, deep learning models may be included for biometric identification using images of the user's iris from the inward-facing cameras. Such models may also be utilized to determine if a user is wearing a contact lens—because the model will jump out in the Fourier transform of the image data from the inward-facing cameras.

The use of outward-facing cameras, such as those depicted in FIG. 16A (124, 154, 156) may be utilized to conduct SLAM or PTAM analysis for the determination of pose, such as the pose of a user's head relative to the environment in which he is present wearing a head-mounted component (58), as described above. Most SLAM techniques are dependent upon tracking and matching of geometric features, as described in the embodiments above. Generally it is helpful to be in a “textured” world wherein the outward-facing cameras are able to detect corners, edges, and other features; further, certain assumptions may be made about the permanence/statics of features that are detected in scenes, and it is helpful to have significant computing and power resources available for all of this mapping and tracking analysis with SLAM or PTAM processes; such resources may be in short supply with certain systems, such as some of those which are portable or wearable, and which may have limited embedded processing capabilities and power available. Deep learning networks may be incorporated into various embodiments to observe differences in image data, and based upon training and configuration, play a key role in the SLAM analysis (in the context of SLAM, the deep networks herein may be deemed “DeepSLAM” networks) of variations of the subject system.

In one embodiment, a DeepSLAM network may be utilized to estimate pose between a pair of frames captured from cameras coupled to a component to be tracked, such as the head mounted component (58) of an augmented reality system. The system may comprise a convolutional neural network configured to learn transformation of pose (for example, the pose of a head mounted component 58) and apply this in a tracking manner. The system may be configured to start looking at a particular vector and orientation, such as straight ahead at a known origin (so 0,0,0 as X, Y, Z). Then the user's head may be moved, for example, to the right a bit, then to the left a bit between frame 0 and frame 1 with the goal of seeking the pose transform or relative pose transformation. The associated deep network may be trained on a pair of images, for example, wherein we know pose A and pose B, and image A and image B; this leads to a certain pose transformation. With the pose transformation determined, one may then integrate associated IMU data (from accelerometers, gyros, etc.—as discussed above) into the pose transformation and continue tracking as the user moves away from the origin, around the room, and at whatever trajectory. Such a system may be termed a “relative pose net”, which as noted above, is trained based upon pairs of frames wherein the known pose information is available (the transformation is determined from one frame to the other, and based upon the variation in the actual images, the system learns what the pose transformation is in terms of translation and rotation). Deep homography estimation, or relative pose estimation, has been discussed, for example, in U.S. Patent Application Ser. No. 62/339,799, which is incorporated by reference herein in its entirety.

When such configurations are utilized to conduct pose estimation from frame 0 to frame 1, the result generally is not perfect, and the system must have a means for dealing with drift. As the system moves forward from frame 1 to 2 to 3 to 4 and estimates relative pose, there is a small amount of error brought in between each pair of frames. This error generally accumulates and becomes a problem (for example, without addressing this error-based drift, the system can end up placing the user and his or her associated system componentry in the wrong location and orientation with pose estimation). In one embodiment, the notion of “loop closure” may be applied to solve what may be termed the “relocalization” problem. In other words, the system may be configured to determine if it has been in a particular place before—and if so, then the predicted pose information should make sense in view of the previous pose information for the same location. For example, the system may be configured such that anytime it sees a frame on the map that has been seen before, it relocalizes; if the translation is off, say by 5 mm in the X direction, and the rotation is off, say by 5 degrees in the theta direction, then the system fixes this discrepancy along with those of the other associated frames; thus the trajectory becomes the true one, as opposed to the wrong one. Relocalization is discussed in U.S. Patent Application Ser. No. 62/263,529, which is incorporated by reference herein in its entirety.

It also turns out that when pose is estimated, in particular by using IMU information (i.e., such as data from associated accelerometers, gyros, and the like, as described above), there is noise in the determined position and orientation data. If such data is directly utilized by the system without further processing to present images, for example, there is likely to be undesirable jitter and instability experienced by the user; this is why in certain techniques, such as some of those described above, Kalman filters, sensor fusion techniques, and smoothing functions may be utilized.

With deep network solutions, such as those described above using convolutional neural nets to estimate pose, the smoothing issue may be addressed using recurrent neural networks, or RNNs, which are akin to a long short term memory network. In other words, the system may be configured to build up the convolutional neural net, and on top of that, the RNN is placed. Traditional neural nets are feed forward in design, static in time; given an image or pair of images, they give you an answer. With the RNN, the output of a layer is added to the next input and fed back into the same layer again—which typically is the only layer in the net; can be envisioned as a “passage through time”—at each point in time, the same net layer is reconsidering a slightly temporally tuned input, and this cycle is repeated.

Further, unlike feed forward nets, an RNN can receive a sequence of values as an input (i.e., sequenced over time)—and can also produce a sequence of values as output. The simple structure of the RNN with built in feedback loop that allows it to behave like a forecasting engine, and the result when combined with the convolutional neural net in this embodiment is that the system can take relatively noisy trajectory data from the convolutional neural net, push it through the RNN, and it will output a trajectory that is much smoother, much more like human motion, such as motion of a user's head which may be coupled to a head mounted component (58) of a wearable computing system.

The system may also be configured to determine depth of an object from a stereo pair of images, wherein you have a deep network and left and right images are input. The convolutional neural net may be configured to output the disparity between left and right cameras (such as between left eye camera and right eye camera on a head mounted component 58); the determined disparity is the inverse of the depth if the focal distance of the cameras is known, so the system can be configured to efficiently calculate depth having the disparity information; then meshing and other processes may be conducted without involving alternative components for sensing depth, such as depth sensors, which may require relatively high computing and power resource loads.

As regards semantic analysis and the application of deep networks to various embodiments of the subject augmented reality configurations, several areas are of particular interest and applicability, including but not limited to detection of gestures and keypoints, face recognition, and 3-D object recognition.

With regard to gesture recognition, in various embodiments the system is configured to recognize certain gestures by a user's hands to control the system. In one embodiment, the embedded processor may be configured to utilize what are known as “random forests” along with sensed depth information to recognize certain gestures by the user. A random forest model is a nondeterministic model which may require a fairly large library of parameters, and may require a relatively large processing and therefore power demand.

Further, depth sensors may not always be optimally suited for reading hand gestures with certain backgrounds, such as desk or tabletops or walls which are near to the depth of the subject hand, due to noise limitations with certain depth sensors and inabilities to determine differences between, for example, 1 or 2 cm in depth accurately. In certain embodiments, random forest type of gesture recognition may be replaced with deep learning networks. One of the challenges in utilizing deep networks for such a configuration is in labelling portions of the image information, such as pixels, as “hand” or “not hand”; training and utilizing deep networks with such segmentation challenges may require doing segmentations with millions of images, which is very expensive and time consuming. To address this, in one embodiment, during training time, a thermal camera, such as those available for military or security purposes, may be coupled to the conventional outward-facing camera, such that the thermal camera essentially does the segmentation of “hand” and “no hand” itself by showing which portions of the image are hot enough to be human hand, and which are not.

With regard to face recognition, and given that the subject augmented reality system is configured to be worn in a social setting with other persons, understanding who is around the user may be of relatively high value—not only for simply identifying other nearby persons, but also for adjusting the information presented (for example, if the system identifies a nearby person as an adult friend, it may suggest that you play chess and assist in that; if the system identifies a nearby person as your child, it may suggest that you go and play soccer and may assist in that; if the system fails to identify a nearby person, or identifies them as a known danger, the user may be inclined to avoid proximity with such person).

In certain embodiments, deep neural network configurations may be utilized to assist with face recognition, in a manner similar to that discussed above in relation to deep relocalization. The model may be trained with a plurality of different faces pertinent to the user's life, and then when a face comes near the system, such as near the head mounted component (58), the system can take that face image in pixel space, translate it, for example, into a 128-dimensional vector, and then use vectors as points in high dimensional space to FIG. out whether this person is present in your known list of people or not. In essence, the system may be configured to do a “nearest neighbor” search in that space, and as it turns out, such a configuration can be very accurate, with false positive rates running in the 1 out of 1,000 range.

With regard to 3-D object detection, in certain embodiments, it is useful to have a deep neural network incorporated which will tell the user about the space they are in from a 3-dimensional perspective (i.e., not only walls, floors, ceiling, but also objects populating the room, such as couches, chairs, cabinets, and the like—not just from a traditional 2-dimensional sense, but from a true 3-dimensional sense). For example, in one embodiment it is desirable for a user to have a model which understands the true volumetric bounds of a couch in the room—so that the user knows what volume is occupied by the volume of the couch in the event that a virtual ball or other object is to be thrown, for example. A deep neural network model may be utilized to form a cuboid model with a high level of sophistication.

In certain embodiments, deep reinforcement networks, or deep reinforcement learning, may be utilized to learn effectively what an agent should be doing in a specific context, without the user ever having to directly tell the agent. For example, if a user wants to always have a virtual representation of his dog walking around the room that he is occupying, but he wants the dog representation to always be visible (i.e., not hidden behind a wall or cabinet), a deep reinforcement approach may turn the scenario into a game of sorts, wherein the virtual agent (here a virtual dog) is allowed to roam around in the physical space near the user, but during training time, a reward is given if the dog stays in acceptable locations from, say T0 to T1, and a penalty is given if the user's view of the dog becomes occluded, lost, or bumps into a wall or object. With such an embodiment, the deep network starts learning what it needs to do to win points rather than lose points, and pretty soon it knows what it needs to know to provide the desired function.

The system may also be configured to address lighting of the virtual world in a manner that approximates or matches the lighting of the actual world around the user. For example, to make a virtual perception blend in as optimally as possible with actual perception in augmented reality, lighting color, shadowing, and lighting vectoring is reproduced as realistically as possible with the virtual objects. In other words, if a virtual opaque coffee cup is to be positioned upon an actual tabletop in a room with yellowish tinted light coming from one particular corner of the room that creates shadowing from the real world objects on the real world table, then optimally the light tinting and shadowing of the virtual coffee cup would match the actual scenario. In certain embodiments, a deep learning model may be utilized to learn the illumination of an actual environment in which the system component is placed. For example, a model may be utilized that, given an image or sequences of images from the actual environment, learns the illumination of the room to determine factors such as brightness, hue, and vectoring by one or more light sources. Such a model may be trained from synthetic data, and from images captured from the user's device, such as from the user's head mounted component (58).

Referring to FIG. 29, a deep learning network architecture which may be called a “Hydra” architecture (272) is illustrated. With such a configuration, a variety of inputs (270), such as IMU data (from accelerometers, gyros, magnetometers), outward-facing camera data, depth sensing camera data, and/or sound or voice data may be channeled to a multilayer centralized processing resource having a group of lower layers (268) which conduct a significant portion of the overall processing, pass their results to a group of middle layers (266), and ultimately to one or more of a plurality of associated “heads” (264) representing various process functionalities, such as face recognition, visual search, gesture identification, semantic segmentation, object detection, lighting detection/determination, SLAM, relocalization, and/or depth estimation (such as from stereo image information, as discussed above).

Conventionally, when using deep networks to achieve various tasks, an algorithm will be built for each task. Thus if it desired to recognize automobiles, then an algorithm will be built for that; if it is desired to recognize faces, then an algorithm will be built for that; and these algorithms may be run simultaneously. If unlimited or high levels of power and computation resource are available, then such a configuration will work well and get results; but in many scenarios, such as the scenario of a portable augmented reality system with a limited power supply and limited processing capability in an embedded processor, computing and power resources can be relatively limited, and it may be desirable to process certain aspects of the tasks together. Further, there is evidence that if one algorithm has knowledge from another, then it makes the second algorithm better. For example, if one deep network algorithm knows about dogs and cats, knowledge transfer (also termed “domain adaptation”) from that may help another algorithm recognize shoes better. So there is reason to have some kind of crosstalk between algorithms during training and inference.

Further, there is a consideration related to algorithm design and modification. Preferably if further capabilities are needed relative to an initial version of an algorithm, one won't need to completely rebuild a new one from scratch. The depicted Hydra architecture (272) may be utilized to address these challenges, as well as the computing and power efficiency challenge, because as noted above, it is the case that there are common aspects of certain computing processes that can be shared. For example, in the depicted Hydra architecture (272), inputs (270), such as image information from one or more cameras, may be brought into the lower layers (268) where feature extraction on a relatively low level may be conducted. For example, Gabor functions, derivatives of Gaussians, things that basically effect lines, edges, corners, colors—these are uniform for many problems at the low level. Thus, regardless of task variation, low level feature extraction can be the same, whether it is the objective to extract cats, cars, or cows—and therefore the computation related thereto can be shared. Hydra architecture (272) is a high-level paradigm which allows knowledge sharing across algorithms to make each better, it allows for feature sharing so that computation can be shared, reduced, and not redundant, and allows one to be able to expand the suite of capabilities without having to rewrite everything - rather, new capabilities may be stacked upon the foundation with the existing capabilities.

Thus, as noted above, in the depicted embodiment, the Hydra architecture represents a deep neural network that has one unified pathway. The bottom layers (268) of the network are shared, and they extract basic units of visual primitives from input images and other inputs (270). The system may be configured to go through a few layers of convolutions to extract edges, lines, contours, junctions, and the like. The basic components that programmers used to feature-engineer, now become learned by the deep network. As it turns out, these features are useful for many algorithms, whether the algorithm is face recognition, tracking, etc. Thus once the lower computational work has been done and there is a shared representation from images or other inputs into all of the other algorithms, then there can be individual pathways, one per problem. Thus on top of this shared representation, there is a pathway that leads to face recognition that is very specific to faces, there's a pathway that leads to tracking that is very specific to SLAM, and so on for the other “heads” (264) of the architecture (272). With such an embodiment, one has all of this shared computation that allows for multiplying additions basically, and on the other hand one has very specific pathways that are on top of the general knowledge and allow one to fine tune and find answers to very specific questions.

Also of value with such a configuration is the fact that such neural networks are designed so that the lower layers (268), which are closer to the input (270), require more computation, because at each layer of computation, the system takes the original input and transforms it into some other dimensional space where typically the dimensionality of things is reduced. So once the fifth layer of the network from the bottom layer is achieved, the amount of computation may be in the range of 20 time less than what was required in the lowest level (i.e., because the input was much larger and much larger matrix multiplication was required). In one embodiment, by the time the system has extracted the shared computation, it's fairly agnostic to the problems that need to be solved. A large portion of the computation of almost any algorithm has been completed in the lower layers, so when new pathways are added for face recognition, tracking, depth, lighting, and the like, these contribute relatively little to the computational constraints—and thus such an architecture provides plenty of capability for expansion.

In one embodiment, for the first few layers, they may be no pooling to retain the highest resolution data; mid layers may have pooling processes because at that point, super high resolution is not needed (for example, super high resolution is not needed to know where the wheel of a car is in a middle layer; one really just needs to know where the nut and bolt is located from the lower levels in high resolution, and then the image data can be significantly shrunk as it is passed to the middle layers for location of the wheel of the car).

Further, once the network has all of the learned connections, everything is loosely wired and the connections are advantageously learned through the data. The middle layers (266) may be configured to start learning parts, for example—object parts, face features, and the like; so rather than simple Gabor functions, the middle layers are processing more complex constructs (i.e., squiggly shapes, shading, etc.). Then as the process moves higher toward the top, there are split-offs into the unique head components (264), some of which may have many layers, and some of which may have few. Again, the scalability and efficiency is largely due to the fact that a large portion, such as 90%, of the processing flops are within the lower layers (268), then a small portion, such as 5% of the flops, are at the middle layers (266), and another 5% is in the heads (264).

Such networks may be pre-trained using information that already exists. For example, in one embodiment, ImageNet, a large group (in the range of 10 million) of images from a large group of classes (in the range of 1,000) may be utilized to train all of the classes. In one embodiment, once it's trained, the top layer that distinguishes the classes may be thrown out, but all of the weights learned in the training process are kept.

Referring to FIG. 30A, a pair of coils (302, 304) is shown in a configuration with a particular radius and spacing therebetween, which may be known as a “Helmholtz coil.”

Helmholtz coils come in various configuration (here a pair a round coils are shown) and are known for producing a relatively uniform magnetic field through a given volume, such as that depicted in FIG. 30B (306); magnetic field lines are shown with arrows about the cross sectional views of the coils (302, 304) of FIG. 30B. FIG. 3 illustrates a three-axis Helmholtz coil configuration wherein three pairs (310, 312, 314) are orthogonally oriented as shown. Other variations of Helmholtz or Merritt coils, such as those featuring squared coils, also may be utilized to create predictable and relatively uniform magnetic fields through given volumes. In one embodiment, a Helmholtz type coil may be utilized to assist in calibrating the orientation determining relationship between two sensors operatively coupled to a head mounted component (58) such as those described above. For example, referring to FIG. 30D, head mounted component (58) coupled to an IMU (102) and electromagnetic field sensor (604), as described above, may be placed within a known magnetic field volume of a Helmholtz coil pair (302, 304). With current applied through the coil pair (302, 304), the coils may be configured to generate magnetic fields at selectable frequencies. In one embodiment, the system may be configured to energize the coils at a direct current level to produce a directly-readable output from the magnetometer component of the IMU (102); then the coils may be energized at an alternating current level, for example, to produce a directly-readable output from the electromagnetic localization receiver coil (604). Since those applied fields in such a configuration are generated by the same physical coils (302, 304), they are registered with each other and we know that the fields must have the same orientation. Thus we may read the values from the IMU (102) and electromagnetic field sensor (604) and directly measure a calibration which may be utilized to characterize any difference in orientation readings between the two devices (102, 604) in three dimensions—thus providing a usable calibration between the two for runtime. In one embodiment, the head mounted component (58) may be electromechanically reoriented for further testing relative to the coil set (302, 304). In another embodiment, the coil set (302, 304) may be electromechanically reoriented for further testing relative to the head mounted component (58). In another embodiment, the head mounted component (58) and coil set (302, 304) may be electromechanically reorientable relative to each other. In another embodiment, a three-axis Helmholtz coil, such as that depicted in FIG. 30C, or other more sophisticated magnetic field producing coil, may be utilized to generate magnetic fields and components without the need for reorientation of the head mounted component (58) relative to the coil set (302, 304) for additional testing data.

Referring to FIG. 30E, the system or subsystem being utilized in such calibration configurations to produce a predictable magnetic field, such as a pair of coils (302, 304) in a Helmholtz type of configuration, may have one or more optical fiducials (316) coupled thereto, such that the one or more cameras (124) which may comprise the head mounted component (58) may view such fiducials. Such a configuration provides an opportunity to ensure that the electromagnetic sensing subsystem is aligned in a known way with the cameras. In other words, with such a configuration, one has optical fiducials physically coupled or anchored to the magnetic field generating device in a known or measured fashion (for example, an articulated coordinate measurement machine may be utilized to establish the precise X, Y, Z coordinates of each fiducial location 316); the head mounted component (58) may be placed inside of the testing volume and exposed to the magnetic field, while the cameras (124) of the head mounted component (58) observe one or more fiducials (316) and thus calibrate the extrinsics of the magnetic field sensors and the cameras (because the magnetic field generator is attached to the fiducials that the cameras are observing). The optical fiducials (316) may comprise flat features such as checkerboards, aruco markers, textured or otherwise three-dimensional features. The optical fiducials may also be dynamic, such as in a configuration wherein small displays, such as LCD displays, are utilized; they may be static and printed out; they may be etched with lasers or chemistry into a substrate material; they may comprise coatings or anodizing or other features recognizable by the cameras (124). In a factory calibration setting, a plurality of calibration systems, such as those described herein, may be located adjacent one another, and may be timed such that adjacent systems do not produce magnetic fields that would interfere with readings at an adjacent system. In one embodiment a group of calibration stations maybe time sequenced; in another embodiment every other, or every second, or every third, and so on, may be simultaneously operated to provide functional separation.

FIG. 31 illustrates a simplified computer system 3100 according to an embodiment described herein. Computer system 3100 as illustrated in FIG. 31 may be incorporated into devices described herein. FIG. 31 provides a schematic illustration of one embodiment of computer system 3100 that can perform some or all of the steps of the methods provided by various embodiments. It should be noted that FIG. 31 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. FIG. 31, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner.

Computer system 3100 is shown comprising hardware elements that can be electrically coupled via a bus 3105, or may otherwise be in communication, as appropriate. The hardware elements may include one or more processors 3110, including without limitation one or more general-purpose processors and/or one or more special-purpose processors such as digital signal processing chips, graphics acceleration processors, and/or the like; one or more input devices 3115, which can include without limitation a mouse, a keyboard, a camera, and/or the like; and one or more output devices 3120, which can include without limitation a display device, a printer, and/or the like.

Computer system 3100 may further include and/or be in communication with one or more non-transitory storage devices 3125, which can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory (“ROM”), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

Computer system 3100 might also include a communications subsystem 3119, which can include without limitation a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMax device, cellular communication facilities, etc., and/or the like. The communications subsystem 3119 may include one or more input and/or output communication interfaces to permit data to be exchanged with a network such as the network described below to name one example, other computer systems, television, and/or any other devices described herein. Depending on the desired functionality and/or other implementation concerns, a portable electronic device or similar device may communicate image and/or other information via the communications subsystem 3119. In other embodiments, a portable electronic device, e.g., the first electronic device, may be incorporated into computer system 3100, e.g., an electronic device as an input device 3115. In some embodiments, computer system 3100 will further comprise a working memory 3135, which can include a RAM or ROM device, as described above.

Computer system 3100 also can include software elements, shown as being currently located within the working memory 3135, including an operating system 3140, device drivers, executable libraries, and/or other code, such as one or more application programs 3145, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the methods discussed above, might be implemented as code and/or instructions executable by a computer and/or a processor within a computer; in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer or other device to perform one or more operations in accordance with the described methods.

A set of these instructions and/or code may be stored on a non-transitory computer-readable storage medium, such as the storage device(s) 3125 described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system 3100. In other embodiments, the storage medium might be separate from a computer system e.g., a removable medium, such as a compact disc, and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by computer system 3100 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on computer system 3100 e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc., then takes the form of executable code.

Various exemplary embodiments of the invention are described herein. Reference is made to these examples in a non-limiting sense. They are provided to illustrate more broadly applicable aspects of the invention. Various changes may be made to the invention described and equivalents may be substituted without departing from the true spirit and scope of the invention. In addition, many modifications may be made to adapt a particular situation, material, composition of matter, process, process act(s) or step(s) to the objective(s), spirit or scope of the present invention. Further, as will be appreciated by those with skill in the art that each of the individual variations described and illustrated herein has discrete components and features which may be readily separated from or combined with the features of any of the other several embodiments without departing from the scope or spirit of the present inventions. All such modifications are intended to be within the scope of claims associated with this disclosure.

The invention includes methods that may be performed using the subject devices. The methods may comprise the act of providing such a suitable device. Such provision may be performed by the end user. In other words, the “providing” act merely requires the end user obtain, access, approach, position, set-up, activate, power-up or otherwise act to provide the requisite device in the subject method. Methods recited herein may be carried out in any order of the recited events which is logically possible, as well as in the recited order of events.

Exemplary aspects of the invention, together with details regarding material selection and manufacture have been set forth above. As for other details of the present invention, these may be appreciated in connection with the above-referenced patents and publications as well as generally known or appreciated by those with skill in the art. The same may hold true with respect to method-based aspects of the invention in terms of additional acts as commonly or logically employed.

In addition, though the invention has been described in reference to several examples optionally incorporating various features, the invention is not to be limited to that which is described or indicated as contemplated with respect to each variation of the invention. Various changes may be made to the invention described and equivalents (whether recited herein or not included for the sake of some brevity) may be substituted without departing from the true spirit and scope of the invention. In addition, where a range of values is provided, it is understood that every intervening value, between the upper and lower limit of that range and any other stated or intervening value in that stated range, is encompassed within the invention.

Also, it is contemplated that any optional feature of the inventive variations described may be set forth and claimed independently, or in combination with any one or more of the features described herein. Reference to a singular item, includes the possibility that there are plural of the same items present. More specifically, as used herein and in claims associated hereto, the singular forms “a,” “an,” “said,” and “the” include plural referents unless the specifically stated otherwise. In other words, use of the articles allow for “at least one” of the subject item in the description above as well as claims associated with this disclosure. It is further noted that such claims may be drafted to exclude any optional element. As such, this statement is intended to serve as antecedent basis for use of such exclusive terminology as “solely,” “only” and the like in connection with the recitation of claim elements, or use of a “negative” limitation.

Without the use of such exclusive terminology, the term “comprising” in claims associated with this disclosure shall allow for the inclusion of any additional element—irrespective of whether a given number of elements are enumerated in such claims, or the addition of a feature could be regarded as transforming the nature of an element set forth in such claims. Except as specifically defined herein, all technical and scientific terms used herein are to be given as broad a commonly understood meaning as possible while maintaining claim validity.

The breadth of the present invention is not to be limited to the examples provided and/or the subject specification, but rather only by the scope of claim language associated with this disclosure. 

1. (canceled)
 2. A method of resolving hemisphere ambiguity at a system comprising one or more sensors, the method comprising: determining, by one or more sensors positioned within a headset of the system, a first position and a first orientation of a hand-held controller of the system within a first hemisphere with respect to the headset; determining a second position and a second orientation of the hand-held controller within a second hemisphere with respect to the headset, wherein the second hemisphere is diametrically opposite the first hemisphere with respect to the headset; determining a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere; and determining, based on the position vector, that: the first position and the first orientation of the hand-held controller is accurate; or the second position and the second orientation of the hand-held controller is accurate.
 3. The method of claim 2, wherein the position vector is defined at a coordinate frame of the headset.
 4. The method of claim 2, further comprising: determining a normal vector with respect to the headset, wherein the normal vector originates from the headset and extends at an angle down from a horizontal line from the headset.
 5. The method of claim 4, further comprising: determining, based on a geometric relationship between the position vector and the normal vector, that: the first position and the first orientation of the hand-held controller is accurate; or the second position and the second orientation of the hand-held controller is accurate.
 6. The method of claim 4, further comprising: determining that the first position and the first orientation of the hand-held controller is accurate when an angle between the normal vector and the position vector is less than 90 degrees, and determining that the second position and the second orientation of the hand-held controller is accurate when the angle between the normal vector and the position vector is greater than 90 degrees.
 7. The method of claim 2, wherein when the first position and the first orientation of the hand-held controller is accurate, the first hemisphere is identified as a front hemisphere with respect to the headset and the second hemisphere is identified as a back hemisphere with respect to the headset.
 8. The method of claim 2, wherein when the second position and the second orientation of the hand-held controller is accurate, the second hemisphere is identified as a front hemisphere with respect to the headset and the first hemisphere is identified as a back hemisphere with respect to the headset.
 9. The method of claim 2, further comprising: delivering virtual content to a display based on: the first position and the first orientation, when the first position and the first orientation of the hand-held controller is accurate; or the second position and the second orientation, when the second position and the second orientation of the hand-held controller is accurate.
 10. The method of claim 2, wherein the system is an optical device.
 11. The method of claim 2, wherein the method is performed during an initialization process of the headset.
 12. A system comprising: a headset comprising one or more sensors; a processor coupled to the headset configured to perform operations including: determining, by the one or more sensors positioned within the headset, a first position and a first orientation of a hand-held controller of the system within a first hemisphere with respect to the headset; determining a second position and a second orientation of the hand-held controller within a second hemisphere with respect to the headset, wherein the second hemisphere is diametrically opposite the first hemisphere with respect to the headset; determining a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere; and determining, based on the position vector, that: the first position and the first orientation of the hand-held controller is accurate; or the second position and the second orientation of the hand-held controller is accurate.
 13. The system of claim 12, wherein the position vector is defined at a coordinate frame of the headset.
 14. The system of claim 12, wherein the processor is further configured to perform operations including: determining a normal vector with respect to the headset, wherein the normal vector originates from the headset and extends at an angle down from a horizontal line from the headset.
 15. The system of claim 14, wherein the processor is further configured to perform operations including: determining, based on a geometric relationship between the position vector and the normal vector, that: the first position and the first orientation of the hand-held controller is accurate; or the second position and the second orientation of the hand-held controller is accurate.
 16. The system of claim 14, wherein the processor is further configured to perform operations including: determining that the first position and the first orientation of the hand-held controller is accurate when an angle between the normal vector and the position vector is less than 90 degrees, and determining that the second position and the second orientation of the hand-held controller is accurate when the angle between the normal vector and the position vector is greater than 90 degrees.
 17. The system of claim 12, wherein when the first position and the first orientation of the hand-held controller is accurate, the first hemisphere is identified as a front hemisphere with respect to the headset and the second hemisphere is identified as a back hemisphere with respect to the headset.
 18. The system of claim 12, wherein when the second position and the second orientation of the hand-held controller is accurate, the second hemisphere is identified as a front hemisphere with respect to the headset and the first hemisphere is identified as a back hemisphere with respect to the headset.
 19. The system of claim 12, wherein the processor is further configured to perform operations including: delivering virtual content to a display based on: the first position and the first orientation, when the first position and the first orientation of the hand-held controller is accurate; or the second position and the second orientation, when the second position and the second orientation of the hand-held controller is accurate.
 20. The system of claim 12, wherein the operations are performed during an initialization process of the headset.
 21. A computer-program product embodied in a non-transitory computer-readable medium, the non-transitory computer-readable medium having stored thereon a sequence of instructions which, when executed by a processor, causes the processor to execute a method for resolving hemisphere ambiguity at a system comprising one or more sensors comprising: determining, by one or more sensors positioned within a headset of the system, a first position and a first orientation of a hand-held controller of the system within a first hemisphere with respect to the headset; determining a second position and a second orientation of the hand-held controller within a second hemisphere with respect to the headset, wherein the second hemisphere is diametrically opposite the first hemisphere with respect to the headset; determining a position vector identifying a position of the hand-held controller with respect to the headset in the first hemisphere; and determining, based on the position vector, that: the first position and the first orientation of the hand-held controller is accurate; or the second position and the second orientation of the hand-held controller is accurate. 